Re: Avoiding the == blues

Even easier, use warnings or -w:

>perl -w
my $splort;
if( $splort = 0 ) {
   print 'narf!';
}
^Z
Found = in conditional, should be == at - line 2.
[download]

Examine what is said, not who speaks.

Silence betokens consent.

Love the truth but pardon error.

Comment on Re: Avoiding the == blues Download Code

Replies are listed 'Best First'.
Re^2: Avoiding the == blues (!trivial) by tye (Sage) on Dec 29, 2004 at 19:59 UTC
That is not nearly as useful as it only catches trivial cases: `> perl -w use strict; my $bool = 0; if( $bool = 0 ) { print "never\n"; } <EOF> Found = in conditional, should be == at - line 3. > perl -w use strict; my $bool = 0; sub test { return 0 == @ARGV } if( $bool = test() ) { print "Match\n"; } <EOF> Match` [download] - tye	[reply] [d/l]
Re^2: Avoiding the == blues by friedo (Prior) on Dec 29, 2004 at 20:00 UTC
You are absolutely correct, of course, but this doesn't work for other languages, or for badly written scripts which generate thousands of warnings that you have to maintain. :)	[reply]
Re^3: Avoiding the == blues by gaal (Parson) on Dec 29, 2004 at 20:26 UTC
In some other languages, `if` takes a boolean, which is (deliberately) not what an assignment returns, so `if (x = 0)` doesn't get past the compiler.	[reply] [d/l] [select]
Re^3: Avoiding the == blues by Anonymous Monk on Dec 30, 2004 at 10:07 UTC
Well, saying "other languages" isn't quite correct, as it's the compiler that will issue a warning, if any. And gcc with -Wall will. It will even catch cases like: `if (x = y)` [download] unlike Perls -w, which will let you do `if ($x = $y)` [download] while keeping silent.	[reply] [d/l] [select]