You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Nathan Bubna <nb...@gmail.com> on 2009/03/13 02:18:19 UTC

#set null in 2.0

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-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


Re: #set null in 2.0

Posted by ap...@recks.org.
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,
Christoph

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.
> 
> 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-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


Re: #set null in 2.0

Posted by Nathan Bubna <nb...@gmail.com>.
On Thu, Mar 12, 2009 at 9:07 PM, Will Glass-Husain
<wg...@gmail.com> 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 <nb...@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-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: dev-help@velocity.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


Re: #set null in 2.0

Posted by Will Glass-Husain <wg...@gmail.com>.
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 <nb...@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-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


Re: #set null in 2.0

Posted by Byron Foster <by...@base2.cc>.
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-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org