1. You don't say in your RFC, but I'm guessing, that a null value
evaluates to false in a boolean context. Correct?

2. In your abstract, you say that undef is used to mean that a 
variable's value is undefined, which I presume means uninitialized.
You say that null would provide a useful way to indicate that a
variable's value is known to be unknown or not applicable. Then, 
at various places in the RFC, you use a hypothetical 
    use initialize 'null';
construct to initialize all new variables to null. Doesn't that 
defeat the purpose, and make null equivalent to undef?

3. Your RFC does not specify how a null value stringizes. What
is the output from:

    $a = null;
    print "a is '$a'";

I can see two possibilities: "a is ''" and "a is 'null'". 
I personally would greatly prefer the first.
Would the use of a null value in a string generate a warning, as
an undef value does now?

 ----------------------------------------------------------------------
 Eric J. Roode,  [EMAIL PROTECTED]           print  scalar  reverse  sort
 Senior Software Engineer                'tona ', 'reh', 'ekca', 'lre',
 Myxa Corporation                        '.r', 'h ', 'uj', 'p ', 'ts';

Reply via email to