New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strict errors in eval very hard to detect #480
Comments
From tchrist@jhereg.perl.com------- Forwarded Message Date: Mon, 06 Sep 1999 04:51:55 GMT [posted & mailed] Sean McAfee wrote:
Could be. This has been mentioned here a couple of times before. http://x46.deja.com/getdoc.xp?AN=483645444
I remember this trick from Mike Guy to check compilation with eval. use strict; It could still have side effects if you have BEGIN or use in $code, I'd at least like to see $@ =~ /eval had compilation errors/ when the - -- ------- End of Forwarded Message Witness this code: # warntester my($str,$retval); $^W = 0; # absolutely no warnings # XXX: this "can't" happen numout(); $str = q{ print $x }; if ( $retval = eval $str; close STDOUT; sub numout { That produces: 1: Leaked warning: Global symbol "$x" requires explicit package name at (eval 1) line 2. First of all, that shouldn't be a warning when it's going to terminate This makes it impossible to employ the important strict pragma for a --tom |
From @gsarOn Mon, 06 Sep 1999 10:21:08 MDT, Tom Christiansen wrote:
Thanks for that test case. I think this patch addresses everything Sarathy Inline Patch
|
Migrated from rt.perl.org#1321 (status was 'resolved')
Searchable as RT1321$
The text was updated successfully, but these errors were encountered: