Hi,
when I'm debugging (which is quite near to optimising them), I'm simply
adding
use strict;
use diagnosticts;
use warnings;
thats all, when your program starts without complaints, you're good...
To get to a lower level: use algorithm-flow-charts to visualise your
program, and then optimise it
> o The Camel Book "Programming Perl" (3rd Edition) by O'Reilly Associates
> has a section in the back about making Perl code faster, as far as I
> remember
Second edition:
http://www.bluesreview.com/Oreilly/perl/prog/index.htm
8.3 Efficiency
http://www.bluesreview.com/Oreilly/perl/prog/ch08
>> Nafiseh wrote:
> thx a lot...
> but
> do u know that ..is it possible that router put their data
> in database and not in file...to process it faster..
>
Nafiseh,
That really depends ... databases can be faster, but then so can text files
...
o http://www.perl.com/pub/a/2001/04/10/engine.
Nafiseh,
The first rule of optimisation is:
"Don't talk about optimisation".
The second rule of optimisation is:
"Don't talk about optimisation".
The third rule of optimisation is:
"Don't optimise".
More seriously, if you're having to optimise your code to run faster, you
probably shouldn't be
