On Sat, Aug 05, 2000 at 10:15:32AM -0700, Nathan Wiger wrote: > Don't make me field calls like this, PLEASE. Perl already has the > ability to turn strict on for projects where it's needed. If you can't > trust one of your programmers to type: > use strict; > use warnings; > How can you trust *any* of the code they produce?!?! Because perl is for the lazy. I want an easy way to arrange for all my programs to run under strict/warnings, should that be my inclination. Can't we make everyone happy by making it a build-time option?
- Clarification on Default Scoping (w... Nathan Wiger
- Re: Clarification on Default Sc... Mark-Jason Dominus
- Re: Clarification on Default Sc... Peter Scott
- Re: Clarification on Default Sc... mjd-perl-list-language-strict
- Re: Clarification on Default Sc... Ted Ashton
- Re: Clarification on Default Sc... Bart Lateur
- Re: Clarification on Default Sc... Ted Ashton
- Re: Clarification on Default Sc... Bart Lateur
- Re: Clarification on Default Sc... Monty Taylor
- Re: C<strict> as default (was Re: RFC ... Nathan Wiger
- Re: C<strict> as default (was Re:... Michael Stevens
- Re: C<strict> as default (was... mjd-perl-list-lang-strict
- Re: C<strict> as default ... Michael Stevens
- Re: C<strict> as default ... Peter Scott
- Re: C<strict> as default ... Peter Scott
- Re: C<strict> as default ... Johan Vromans
- Re: C<strict> as default (was... Nathan Wiger
- Re: C<strict> as default (was... Bryan C . Warnock
- Re: C<strict> as default (was Re: RFC ... Piers Cawley
