Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
- From: Ilya Zakharevich <nospam-abuse@xxxxxxxxx>
- Date: Sun, 3 Jan 2010 01:39:40 +0000 (UTC)
On 2009-12-30, Ben Morrow <ben@xxxxxxxxxxxx> wrote:
[2] I remember the bad old days of C programming where you could choose
between getting lots of warnings from system header files and turning
off many useful warnings.
This is not my experience with using -w. At least not for a decade.
This will be because most modules 'use warnings', and 'no warnings'
where they need to, which overrides -w.
I call this BS:
.cpan\build>pfind . "/\.pm$/" "=~ /\b use \s+ warnings \b/x" du
9192861 bytes in 932 files, 0 directories
.cpan\build>pfind . "/\.pm$/" du
89051284 bytes in 4312 files, 0 directories
The numbers are duplicated due to ./blib/*, but it does not change
the ratio (which is 10% in metric of byte-of-code ;-).
Yours,
Ilya
.
- Prev by Date: Re: My grandmother installs modules better than yours
- Next by Date: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
- Previous by thread: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
- Next by thread: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
- Index(es):
Relevant Pages
|
