DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31189>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31189 ------- Additional Comments From [EMAIL PROTECTED] 2006-03-21 21:16 ------- Paul, I support your view. I think id a particular method or property of an object can not be resolved then throw some exception. I like your idea of passing a switch. Thanks, Roy. (In reply to comment #0) > Currently JEXL is very tolerant with null (and unresolved variables)... > I am unsure now but I think null will become false if the output of a test, null will become the empty > string if concatenated to a string, null will become the number zero when added. Moreover, > invoking a method on null gives you... null... > I would love a switch that just disables all this (I think this would impact quite a lot) allowing my jexl > snippets to be quite more predictable! > paul -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]