in reply to "warn" is your best friend

Actually I find a good IDE, breakpoints and variable contents viewing a lot more powerful and much faster than any sort of print/warn/::diag/Carp/... based technique. Even the Perl command line debugger is vastly quicker for resolving issues than any print based technique (I used Perl's command line debugger for the first time in 3 years yesterday and was sufficiently up to speed with it in 10 minutes).

I use Carp for reporting bad states (unexpected parameters for example) and die for exception handling internally. Those often point to areas where a little debugging is required, but then it's set a breakpoint and inspect the state directly - even changing variable contents on the fly to explore issues further. For me with, any half decent development environment available, print based debugging stopped 30 years ago.

If the code changes take longer than the time saved, it's fast enough already.

Replies are listed 'Best First'.
Re^2: "warn" is your best friend
by bigj (Monk) on Apr 07, 2014 at 02:20 UTC
    Actually, it's best to just log everything. And yes, you are right, there had been vim and emacs available 30 years ago.


Re^2: "warn" is your best friend
by Anonymous Monk on Mar 30, 2014 at 20:13 UTC
    ugh, reading talks like this make me wonder why anyone uses java...