Re: Print Vs Return In a Subroutine

You're micro-optimizing. Stop it.

Just make your code work, and when you think it woks too slow, benchmark the likely culprits and improve those, if necessary.

With Time::HiRes you can get the current time in microseconds, so you can measure quite precisely how long a piece of code takes.

Comment on Re: Print Vs Return In a Subroutine

Replies are listed 'Best First'.
Re^2: Print Vs Return In a Subroutine by chrestomanci (Priest) on Mar 30, 2012 at 12:38 UTC
Agreed, premature optimizing is a bad thing. Also in the not recommended category is trying to write your own profiler by peppering your code with calls to `Time::HiRes::time`. Much better to run the code through a proper profiler such as Devel::NYTProf, that will do a much better job, will profile everything including the stuff you did not think was a bottleneck, and will give you a nicely formatted report to look at.	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Print Vs Return In a Subroutine
by chrestomanci (Priest) on Mar 30, 2012 at 12:38 UTC

Agreed, premature optimizing is a bad thing.

Also in the not recommended category is trying to write your own profiler by peppering your code with calls to Time::HiRes::time. Much better to run the code through a proper profiler such as Devel::NYTProf, that will do a much better job, will profile everything including the stuff you did not think was a bottleneck, and will give you a nicely formatted report to look at.

[reply]
[d/l]