I read in a previous post that the option to turn on behaviour which allows assignment of nulls - ie:
#set( $foo = $someobject.Somemethod ) where Somemethod returns a null, and $foo is not changed. I understood this will be available in 1.5 - however this has caused at least two very serious issues with clients. I know there are work arounds - the problem is that coders that are experienced in velocity still get caught by it, and it can badly mess up reporting. This almost resulted in legal action against us in one instance. How far is 1.5 away from being implemented in the main branch? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
