Re: catastrophic near misses in Perl

Search for "don't use", you'll find lots of things that people recommend not to use, sometimes with good reason.

Comment on Re: catastrophic near misses in Perl

Replies are listed 'Best First'.
Re^2: catastrophic near misses in Perl by Marshall (Canon) on Apr 18, 2009 at 10:15 UTC
I think better is to emphasize what TO DO rather what not. At the very top of my list is: 1. Always "use strict;" - this is a compile time directive and has no run time penalty. 2. Almost always run with run time warnings enabled. Turning this off for well debugged apps that are extremely performance critical and written by experienced Perl programmers can be considered. However this should never be your first thought about "how to I speed this up?".	[reply]

Replies are listed 'Best First'.

Re^2: catastrophic near misses in Perl
by Marshall (Canon) on Apr 18, 2009 at 10:15 UTC

At the very top of my list is:
1. Always "use strict;" - this is a compile time directive and has no run time penalty.
2. Almost always run with run time warnings enabled. Turning this off for well debugged apps that are extremely performance critical and written by experienced Perl programmers can be considered. However this should never be your first thought about "how to I speed this up?".

[reply]