Re: map and undef - odd behaviour with an array of arrays

Running:

use Data::Dumper;
$x[0]=[0];map{undef $_}(@x);print "still defined\n" if defined @x;
print Dumper(\@x);
[download]

produces:

defined(@array) is deprecated at undef1.pl line 2.
    (Maybe you should just omit the defined()?)
still defined
$VAR1 = [
          undef
        ];
[download]

I trust that clarifies what is going on. That is, your array contains a single element with the value undef. Note that an array containing a single element with an undef value is not undef, not even false in scalar context. To be false in scalar context, the array needs to be empty.

Oh, and please heed the deprecated warning and replace "if defined @x" with simply "if @x" (see defined for why).

Comment on Re: map and undef - odd behaviour with an array of arrays Select or Download Code

Replies are listed 'Best First'.
Re^2: map and undef - odd behaviour with an array of arrays by Melly (Chaplain) on Dec 22, 2012 at 08:45 UTC
But why did map{undef $_}(@x) behave differently than undef @x? Edit to add - oh, I'm being stupid - it's undefining each element rather than @x. When I was testing this, for some reason I concluded that perl -e "@x=qw(a);map{undef $_}(@x);print 1 if defined @x;" didn't print 1 (but it does). One of those days... `map{$a=1-$_/10;map{$d=$a;$e=$b=$_/20-2;map{($d,$e)=(2$d$e+$a,$e2 -$d2+$b);$c=$d2+$e2>4?$d=8:_}1..50;print$c}0..59;print$/}0..20` [download] Tom Melly, pm (at) cursingmaggot (stop) co (stop) uk	[reply] [d/l]
Re^3: map and undef - odd behaviour with an array of arrays by eyepopslikeamosquito (Archbishop) on Dec 22, 2012 at 08:53 UTC
But why did map{undef $_}(@x) behave differently than undef @x? `"undef @x"` empties the array while `"map{undef $_}@x"` sets each element in the array to the value undef. Since your array had one element in it, that element was not deleted, rather its value was set to undef.	[reply] [d/l] [select]