Re: RFC 263 (v1) Add null() keyword and fundamental data type

[Tom Christiansen]

>> I'm not happy with your use of "coerce".  There's no mutation.  It simply
>> *is* those things.

>Fine.  So, in particular, it _isn't_ null.

Of course it's null.  That's why it has length zero.  Stop speaking
SQL at me.  I'm speaking Perl.

>> 4) The antiļinitialized value is autovivified to a true value when
>>     used that value is (legally) used lvaluably.

>If, by "true value" in the above, you mean a value other than undef whic<SNIP>
>interpreted as boolean false, then I think I understand what you said.  <SNIP>
>enough to have said it, which is why I used coerce.

No, I mean this:

    undef $a;
    @$a = ();
    if ($a) { ..... } # always true

It's the lvaluable deref that autoinitializes.

--tom