>>syntax variances between them should be limited >>primarily to _new_ functions and tags
I agree with you, but the case of empty values in CF is not syntax variance, the syntax is the same. It is actually a bug, for the least a flaw in the design in ColdFusion. Further more, making the function work properly has no or very little impact on existing applications: 1. if a current application has NO empty values in lists, it will still work the same way; 2. If the progammers already broke their nose on the problem, they have implemented some workaround, and this workaround will still work the same way. 3. If a current application may have some empty list elements in the future, the application will still work properly instead of breaking. .... So where is the problem? Only in the case a programmer exploited this weird behaviour in purpose, and I do not think there must be a lot of such cases. Allaire never admitted it was a bug, because it was THEIR product, MM never did either, because it is THEIR product, for BlueDragon, it is THEIR product also, but not their language, and there is nothing wrong correcting someone else's bugs. -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:197751 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
