>>>>> "MGS" == Michael G Schwern <[EMAIL PROTECTED]> writes:
MGS> You put "no warnings" at the top of the program before you ship it.
MGS> Because "use warnings" has lexical scope, any libraries and modules
MGS> are left unmodified. So one file in your build need be modified.
MGS> Is this too much to ask?
(I'm not against your idea, I hope I'm helping you fine tune it, with
some of my negative experiences.)
A minor nit.
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.
The one that get's me the most is the undef warning. I like to know
that it catches unexpected undef's. But what if I'm working with
real undef's? All that noise hides the real problems.
Perhaps if -w has a level. (Somewhat coarser than lexical. With a family
of these 'known' warnings not emitted.)
<chaim>
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
