Re: Driving maniacally with the debugger

"...step through code...find myself outside of the code...Just Perl and what comes with it"

What about the old school/poor man's approach: use constant DEBUG => 1;? Then print or say, printf, Data::Dumper or Data::Dump, Sys::Syslog bla... if DEBUG. No performance impact if DEBUG is false as far as i understood. And probably you make some poor admins happy when they are on night shift. Please feel free to correct me if i miss the point. Best regards, Karl

ŤThe Crux of the Biscuit is the Apostropheť

perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help

Comment on Re: Driving maniacally with the debugger Select or Download Code

Replies are listed 'Best First'.
Re^2: Driving maniacally with the debugger by ExReg (Priest) on Sep 05, 2017 at 14:20 UTC
I have found myself using the `use constant DEBUG => 1` approach frequently. My problem is that I just like to grab the keys, put the top down, and drive through the code with just occasional glances at the road signs. Just need to be a little more disciplined...	[reply] [d/l]