You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by bu...@apache.org on 2001/10/16 23:13:19 UTC

DO NOT REPLY [Bug 4209] - Assigning null value to variable appears to be a no-op

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4209>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4209

Assigning null value to variable appears to be a no-op

geirm@optonline.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From geirm@optonline.net  2001-10-16 14:13 -------
Hm.  Your observation is valid.  This behavior is consistant with #set()
where

#set($foo = <something that returns null>)

leaves $foo unchanged. We deal with this using the nullSetEvent() and it 
might make sense to fire that event on a #foreach() null assignment as 
well.

Hm.