On Thu, Mar 12, 2009 at 9:07 PM, Will Glass-Husain <[email protected]> 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, 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). Agreed. Removing options and special cases is a great way to simplify things for both users and developers. Dump the baggage; simplify. > WILL > > On Thu, Mar 12, 2009 at 6:18 PM, Nathan Bubna <[email protected]> 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: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
