I advise people to use "no warnings qw(uninitialized)" from time to time, and it usually sparks a backlash of "Don't do that!" emails, but no one has been able to actually give me a good reason why not. I think it's a similar situation. 90% of the time, you can do it with no problems, but most of the intended audience may not be able to understand when to say when, so the popular consensus is that it's best to just tell people not to do it.
Here's another argument against slurping: When you slurp a file all at once, even if your program isn't using up much of the CPU, on many machines it will slow down performance considerably if you slurp a large file (large, of course, is still sometimes relative). If that is the only thing you are running at the time, it may not make much of a difference, but it is usually not a good idea to assume that. -----Original Message----- From: Dan Muey [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 1:49 PM To: Dan Anderson Cc: Perl Beginners Mailing List Subject: RE: Survey : Max size allowable for slurping files Good comparison, I never see advice to use no warnigns and no strict though :) -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
