On Dec 22, 2003, at 4:46 PM, Mike Kienenberger wrote:
The more I use Velocity, the more I find myself writing hacks to get around
the inability of Velocity to handle nulls as a context attribute value.
Over the last half-year I've been subscribed to the mailing list, I've seen
comments that suggest the current behavior can't be changed because it'd
break backwards compatiblity.
Is there anyone on this mailing list that depends on context attributes not
being set to null when the RHS evalutes to null?
Or are we all silently suffering because of some mythical or implausible use
case that doesn't exist?
[Hey, I never said it was an unbiased poll.]
I don't remember why. There are two aspects to this we should cover, the #set() behavior, and adding a NULL token.
What *would* break if
#set($foo = $thing.returnNull())
did as read?
-- Geir Magnusson Jr 203-247-1713(m) [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
