On Tue, Sep 05, 2000 at 10:32:53AM -0400, Chaim Frenkel wrote:
> (I'm not against your idea, I hope I'm helping you fine tune it, with
> some of my negative experiences.)
That's why I posted it here first. Fire away!
> I don't like to change code before shipping. Just another thing that
> can be forgotten or a slip of the finger, or it defeats the purpose of
> having it automatically on by default.
Yeah, this bothers me, too. I'd say that it should be part of your
build process, but its difficult to safely automate Perl code
modification. Will ponder.
> Perhaps if -w has a level. (Somewhat coarser than lexical. With a family
> of these 'known' warnings not emitted.)
It does.
no warnings 'uninitialized';
Given that "uninitialized value" are some of the most common spurious
warnings, (I personally code to check for definedness) it may make
sense for the default to be the equivalent of:
use warnings;
no warnings 'uninitialized';
Everyone will have their own pet-peeve category of warnings, but I
think keepking uninitialized value warnings off by default will make
many people happy.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
Sometimes these hairstyles are exaggerated beyond the laws of physics
- Unknown narrator speaking about Anime
