Re^4: "possible typo" warnings in modules

Replies are listed 'Best First'.
Re^5: "possible typo" warnings in modules by zentara (Cardinal) on Feb 17, 2007 at 19:47 UTC
I agree they are both throwing proper warnings, but it's clear there is a difference in "compilation phase warnings" and "runtime warnings". The first example stops the compilation dead in it's tracks because of a syntax error. Wheras the programming error is allowed to pass as long as the syntax is correct. I think we are arguing over whether the Perl interpreter does a one pass or two pass scan of the code. I guess it only "appears" to do a syntax scan before it cancels the compilation, but I defer to your greater wisdom that it is actually a one pass operation. It seems to the end user that Perl is checking syntax first, and I see your point that it is a misunderstanding on my part, and the syntax scan is only an illusion. I'm not really a human, but I play one on earth. Cogito ergo sum a bum	[reply]
Re^6: "possible typo" warnings in modules by diotalevi (Canon) on Feb 17, 2007 at 20:51 UTC
Well sure, there's a "second pass." When the code is actually run. Want to get a glimpse of what this stuff looks like when its finished being compiled? Use some of the B:: tools: `perl -MO=Concise your-program.pl`, `perl -MO=Debug your-program.pl<c>, <c>perl -MO=Terse your-program.pl`. ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊	[reply] [d/l] [select]
Re^6: "possible typo" warnings in modules by Joost (Canon) on Feb 17, 2007 at 20:55 UTC
I think you're confusing things: warnings are never fatal, since they don't necessarily indicate a "programming error". Warnings are just hints to the programmer. A syntax error isn't a warning, it's a fatal error. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]