I, for one, have always considered this "feature" to be quite silly ... so please go ahead and drop the config property :-) I can't imagine many users relying on this.
cheers, Marino -----Original Message----- From: Will Glass-Husain [mailto:[EMAIL PROTECTED] Sent: 17. desember 2004 18:40 To: [EMAIL PROTECTED] Subject: null in foreach Hi, Does anyone have any strong opinions about null in foreach? (specifically, reasons why we should not do this patch). http://issues.apache.org/bugzilla/show_bug.cgi?id=27741 Note - I see this as a separate issue from the #set and #if handling of nulls. The problem with #foreach is that when looping through a collection containing a null, if a null is hit the iterator carries the old value rather than a null. This just doesn't make sense to me. The provided patch (by Shinobu - thanks!) fixes it, but uses a config property to use old vs new behavior. I'd like to drop the config property and just make #for work as expected, e.g. return the current value of the collection (null or not). Are there any compatibility issues with this? WILL _______________________________________ Forio Business Simulations Will Glass-Husain phone (415) 440-7500 x89 mobile (415) 235-4293 [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
