What logic do you base this on? As far as I know, arrays are faster, and if you think about it, it makes sense. For lists, CF has to parse the string to get the correct data. For example:
<CFSET List = "Foo@Goo@Moo@Doo@Doo"> <CFOUTPUT>#ListGetAt(List,3,"@")#</CFOUTPUT> In the example above, CF has to parse the string and find the element prior to the 3rd @ sign. Arrays are naturally separated and don't require parsing of any kind. As it stands, if you change your lists to arrays, or arrays to lists, just for a minor speed boost, it probably will not be worth your time. Use what makes sense for your application. ======================================================================= Raymond Camden, Principal Spectra Compliance Engineer for Macromedia Email : [EMAIL PROTECTED] Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: Bryan Love [mailto:[EMAIL PROTECTED]] > Sent: Friday, November 30, 2001 8:33 PM > To: CF-Talk > Subject: RE: ArraySort > > > Actually lists are faster than arrays in CF. Create a list like so: > > Last,First~Last2,First2~Last3,First3 > > use listSort() to sort it out > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
