Re^2: More Misleading Compiler Error Messages

[QM]

in reply to Re: More Misleading Compiler Error Messages
in thread More Misleading Compiler Error Messages

Thanks. I should have said that I figured it out. I guess it was something of a puzzle as well.

I just find it odd that the for loop expression didn't compile, and it's complaining about the my $i, which is bogus. Granted, it pointed out the syntax error, but syntax errors should trump warnings, shouldn't it?

Thanks again!

[Anonymous Monk]

You've obviously never driven your grandmother to the library, have you?

GM: Look out for that bicycle!
GM: Ooh!
GM: The light is red, watch out!
GM: Eek, a tram! Don't drive so fast!
GM: Oh look what a darling kitty!
Me: Where?
GM: There! There behind that window, look!
*CRASH*

[ikegami]

It doesn't realize the warning is related to the syntax error. Given

my $s = shift . '!';
$s+++;

the compile will issue both a warning (Warning: Use of "shift" without parens is ambiguous) and a syntax error (syntax error). As far as perl was concerned, it was the same situation with your code.

Missing and extraneous closers (closing quotes, closing curlies, closing brackets, etc) are notoriously noisy errors. If you get a lot of unusual errors/warnings, chances are that's your problem.

[QM]

I see your point, though your example is lacking.

Yes, $s+++ is a syntax error. However, the previous statement should be completely resolved before the syntax error is encountered. my $s = shift . '!'; is a complete statement.

In my example, the syntax error causes the warning, even though the warning is bogus. Thereafter any statement using that variable also causes a warning. There seems to be some queue for warnings and error messages, and no particular priority.

[ikegami]

The single statement $s+1 = shift . '!'; causes both a warning and an error usefully. That's the usual case.