http://qs321.pair.com?node_id=115173

Put a script in debug mode in a hurry!

Just type 'dbg myscript.pl' to put it in debug mode! It adds '-d' to the shebang line. It's sister, 'udbg' is nearly the same thing (takes the '-d' away).

Probably could use some golfing, but it's always worked for me...

here's 'dbg' 

#!/usr/local/bin/perl 
open INFILE, "$ARGV[0]";
@file = <INFILE>;
close INFILE;
$_ = shift @file;
/^#!/ or die "no shebang, file left untouched";
/-d/ and die "file already in debug mode";
s/$/ -d/;
open OUTFILE, ">@ARGV[0]";
print OUTFILE $_;
for (@file) { print OUTFILE $_ }
close OUTFILE;

[download]

and it's sister, 'udbg' 

#!/usr/local/bin/perl
open INFILE, "$ARGV[0]";
@file = <INFILE>;
close INFILE;
$_ = shift @file;
/-d/ ? s/-d// : die "file not in debug mode, untouched";
open OUTFILE, ">@ARGV[0]";
print OUTFILE $_;
for (@file) { print OUTFILE $_ }
close OUTFILE;

[download]

Replies are listed 'Best First'.
Re: dbg - put any script in debug mode
by merlyn (Sage) on Sep 27, 2001 at 22:00 UTC
[reply]
      This is something I use for scripts that are called by other scripts. If there's a wrapper script that manages flow, for example, it's easier to put the target script in debug mode than to find out where it's being called and put the parameter there. With that in mind, it's much easier.

      MM

[reply]
        Based on painful experience I submit that a complex system of scripts that call other scripts is itself a serious problem. Instead I suggest moving functionality into modules, and making individual scripts wrappers around the appropriate module. Then your wrapper script can be built quite directly by loading a bunch of modules and making the right calls.

        This makes consistent error handling tremendously easier, and with a single confess you can figure out exactly who called what where whenever you want.

[reply]

Back to Cool Uses for Perl