You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2006/03/21 22:16:17 UTC
DO NOT REPLY [Bug 31189] - [jexl] Don't make null convertible into anything
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 ripon@hotmail.com 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org