Hi, I think we should simply remove the option since it was really a backwards compatibility hack. Do we have a null object? We should.
In fact, as a general rule for 2.0 I propose we just fix this stuff and remove the special casing. (Same issue for escaping of characters, by the way). WILL On Thu, Mar 12, 2009 at 6:18 PM, Nathan Bubna <nbu...@gmail.com> wrote: > In 1.x we have: > > directive.set.null.allowed = false > > I think that we should flip that to true and perhaps even remove the > option in 2.0. > > Does anyone out there rely on not being able to change variables to null? > Does anyone out there even remember why it wasn't allowed in the first place? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
