in reply to Re: Breaking The Rules
in thread Breaking The Rules

Your two ways of testing undef don't actually do the same thing. if defined $var will execute your statement if $var is defined. unless $var eq undef will execute your statement if $var is undef, the empty string, or something else that will stringify to the empty string. Try the following code snippet to see for yourself:
my $var = undef; print "Undefined!\n" if $var eq undef; $var = ''; print "Undefined again!\n" if $var eq undef;
This happens because the "eq" operator stringifies both of its arguments, and undef stringifies to the empty string. The warning doesn't exist just to critique your syntax... it's warning you of a danger that your code might not be doing exactly what you think it is.

Replies are listed 'Best First'.
Re^3: Breaking The Rules
by Unanimous Monk (Sexton) on May 31, 2006 at 22:15 UTC
    Hmmm, your right. That’s not how I thought it was working, but it makes sense that it works that way.

    Learn something new everyday! (I apologies if this is what GrandFather was trying to point out, and I was too obtuse to realize it) :)