On Thu, 13 Jan 2005, Randy W. Sims wrote: > But, I don't really worry about it. I've never used anything like that > in my code. If there are speed problems, there are usually better > candidates for optimization. I have never had to remove, or even think > about removing, either pragma for speed considerations. There's a reason that optimization is called the root of all evil.
If your code is running so slowly that you're seriously considering removing strictures & warnings for the negligible speed boost that doing so may bring, you *really* need to reconsider your approach to whatever the problem at hand may be. There is *always* a better and safer place to go optimizing. Yes, warnings can be annoying for backwards-compatible modules, but I think that counts as an esoteric justification for what is otherwise a bad habit. For the bulk of code that has no constraints on 5 or 10 year old versions of Perl, that shouldn't be a problem. -- Chris Devers -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
