On Sun, Aug 06, 2000 at 02:27:00PM -0400, [EMAIL PROTECTED] wrote: > > But I think it would be extremely valuable research if someone would > actually try living with PERL5OPTS='-Mstrict -W' for a month or two. I could live with PERL5OPTS for ages, especially since perl uses PERL5OPT, not PERL5OPTS ;-) However, PERL5OPT seems to have some gross failures: % env PERL5OPT='-Mstrict -W' perl -e 'print $x' % env PERL5OPT='-Mstrict -w' perl -e 'print $x' % env PERL5OPT='-Mstrict' perl -e 'print $x' Global symbol "$x" requires explicit package name at -e line 1. Execution of -e aborted due to compilation errors. % env PERL5OPT='-WMstrict' perl -e 'print $x' Illegal switch in PERL5OPT: -W. This is bleedperl @6534. -- Johan
- Re: Clarification on Default Scopin... Bart Lateur
- Re: Clarification on Default Scopin... Ted Ashton
- Re: Clarification on Default Scopin... Bart Lateur
- Re: Clarification on Default Scopin... Monty Taylor
- Re: C<strict> as default (was Re: RFC 16 (... Nathan Wiger
- Re: C<strict> as default (was Re: RFC... Michael Stevens
- Re: C<strict> as default (was Re:... mjd-perl-list-lang-strict
- Re: C<strict> as default (was... Michael Stevens
- Re: C<strict> as default (was... Peter Scott
- Re: C<strict> as default (was... Peter Scott
- Re: C<strict> as default (was... Johan Vromans
- Re: C<strict> as default (was Re:... Nathan Wiger
- Re: C<strict> as default (was Re:... Bryan C . Warnock
- Re: C<strict> as default (was Re: RFC 16 (... Piers Cawley