For what it is worth, those functions were designed to simplify working with HTML form fields and the like where empty fields are irrelevant. I am neither defending or arguing with the original design, but the fact of the matter is most of us use lists not the way they were intended.
Problem is, think of how much existing code would break if that were changed. The truth is it would be too dangerous to change at this point. But, there is no reason we could not create replacement list functions. I propose we create parallel functions for every list function, call these CSVList...() instead of List...(), so ListGetAt() would map to CSVListGetAt(), ListFirst() would map to CSVListFirst(), and so on. Would be easy to write. Anyone? :-) --- Ben -----Original Message----- From: David Schmidt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 12:42 PM To: CF-Talk Subject: CF Wishlist Ok, Have carefully considered what I want from CF, the most striking feature I want to see is... "Stop treating empty list items as null." That is a list of "3,5,,,3,2,2" should have a length of 7, instead of 5. Doing this would nearly eliminate the need for any field names like name="cost_#i#", since HTML sends back "3,5,,,3,2,2" for duplicate text fields named "cost" anyways. ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. 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
