in reply to CGI.pm and Use of uninitialized value in pattern match
Why not turn off the warnings you don't want?
I mean, isn't that why no warnings exists?
IMHO it needn't be taboo.
All the best, andye
update: after thinking about this a little more, I've decided that what I really mean is: Surely there should be no taboos in programming?
What I'm getting at is that, sure, using strict and warnings is, in general, a good idea - but that shouldn't make them a religious imperative. They're useful for a specific reason, not because it's a Sin to do without them.
If the code is clearer without them - and in my view it is in this case - then switching them off is the Right Thing, no?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: CGI.pm and Use of uninitialized value in pattern match
by afarber (Initiate) on Feb 27, 2009 at 14:05 UTC |
In Section
Seekers of Perl Wisdom