Hi,
> Does anyone out there even remember why it wasn't allowed in the first place?
Several Map implementations do not allow null values, so as the original
Hashtable context implementation.
> Does anyone out there rely on not being able to change variables to null?
not me...
Greetings,
Christ
On Mar 12, 2009, at 18:18 , Nathan Bubna 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.
Agreed.
-
To unsubscribe, e-mail: dev-u
On Thu, Mar 12, 2009 at 9:07 PM, Will Glass-Husain
wrote:
> 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.
We don't need a null object/keyword. $null works fantastically. Keep
it simple.
> In fact,
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
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?
