<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc = "http://purl.org/dc/elements/1.1/" xmlns="http://purl.org/rss/1.0/">
	<channel rdf:about="http://livedocs.adobe.com/">
	<title>LiveDocs Comments - coldfusion - 6 - Migrating_ColdFusion_5_Applications - cf_migration_guide6.htm</title>	
		<link>http://livedocs.adobe.com/</link>
		<description>Macromedia LiveDocs - online documentation with user feedback.</description>
		<copyright>Copyright 2009, Macromedia, Inc.</copyright>
		<dc:date>2009-11-25T08:17:14</dc:date>
		<dc:language>en-us</dc:language>
		<items>
			<rdf:Seq>
				<rdf:li rdf:resource="http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#41857" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#31329" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#3341" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#2203" />
			</rdf:Seq>
		</items>
	</channel>
	
	<item rdf:about="http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#41857">
		<title>coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm</title>
		<link>http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#41857</link>
		<description>From ColdFusion MX on, Structs are an implementation of Java HashMaps, which do not guarantee to keep the order of the keys as they are designed for speedy forward lookup, not for ordered traversal.&lt;br /&gt;&lt;br /&gt;As long as they are unchanged, it is probable that they will be traversed in the same order during their lifetime, but as you add or remove keys, that order will change more or less unpredictably.</description>
		<dc:creator>CmdrTomalak</dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2005-11-04T05:21:11</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#31329">
		<title>coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm</title>
		<link>http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#31329</link>
		<description>I don't see where the MX 6.1 documentation says that using cfloop to loop over a query is done in no particular order.  I see where it says &quot;The StructKeyList and StructKeyArray functions do not return keys in any particular order. Use the ListSort or ArraySort functions to sort the results&quot; but I don't see where it speaks to the issue of order when looping over a structure.&lt;br /&gt;&lt;br /&gt;I haven't done extensive testing at this point, but my preliminary findings indicate that it is not true that looping over a structure or returning its keys with StructKeyList or StructKeyArray happens in no particular order.  I have seen the same order used consistently on the same structure.  However, what that order is I do not know--it isn't the order the keys went into the structure and it isn't alphabetic.  But the point is that there does seem to be some method to the madness and so the claim that &quot;no particular order&quot; is used is incorrect.  Of course, since we as CF developers don't know what that method is and further, since that method doesn't result in any kind of useful ordering of the keys, we have to treat the method like it is random anyway.&lt;br /&gt;&lt;br /&gt;Josh</description>
		<dc:creator>jladams97</dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2005-04-12T09:18:43</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#3341">
		<title>coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm</title>
		<link>http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#3341</link>
		<description>The cloop comment &quot;ColdFusion MX returns struct keys in the order that you create them. ColdFusion 5 returns struct keys in alphabetical order.&quot; is incorrect.&lt;br /&gt;&lt;br /&gt;I have found ColdFusion MX 6.1 returns the keys in no particular order and the MX 6.1 documentation states this in a number of places.</description>
		<dc:creator></dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2003-10-31T09:24:28</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#2203">
		<title>coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm</title>
		<link>http://livedocs.adobe.com/coldfusion/6/Migrating_ColdFusion_5_Applications/cf_migration_guide6.htm#2203</link>
		<description>When using cfdirectory.datelastmodified, keep in mind it is not a date object but a string object. In Coldfusion 5 DateCompare, DateFormat, etc could be done directly on the datelastmodified attribute. With CF MX you need to use a ParseDateTime first to create a date object from it.</description>
		<dc:creator>michaschopman</dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2003-09-28T05:04:08</dc:date>
	</item>
	</rdf:RDF>

