Adblock rules

! Stackoverflow network sites
! Don't distract me please
##DIV[class="module community-bulletin"]
##DIV[id="chat-feature"][class="module"]
##DIV[id="hot-network-questions"][class="module"]

Make "x" use Data::Dumper in the Perl debugger

tldr:

$DB::alias{x} = 's/^x\s+(.*)/p Data::Dumper::Dumper($1)/';

Thanks Jim

Full article:

In the guts of the script that runs the Perl command-line debugger (accessible whenever you start a perl script with the '-d' command-line argument), there lives a hash, accessible globally as %DB::alias.  Whenever you enter a command at the debugger command line, the first word in the command is looked up in %DB::alias, and if it is found, the corresponding value is used as a substitution pattern against the entire command line.  The substituted line is then processed as usual.  The examples and explanation in the perldebug man page don't make this terribly clear.  The actual code that is executed by the debugger (after stuffing the first word in the command line into the variable $i) is:

eval "\$cmd =~ $alias{$i}";

This can be used to completely customize the debugger.  For example, the ordinary output of the debugger's built-in "x" command is pretty ugly.  Substituting a different formatter (such as Data::Dumper::Dumper) can be accomplished with the following alias:

$DB::alias{x} = 's/^x\s+(.*)/p Data::Dumper::Dumper($1)/';

This converts the line "x $something" into the line "p Data::Dumper::Dumper($something)".  Incidentally, solving this particular problem was the impetus for this blog post.

More extensive customization is possible.  For instance, alias substitution occurs once in the stock debugger.  Armed with the knowledge of how alias substitution works, you can create an alias that expands aliases iteratively like this:

my $in_exp = 0;

sub expand_db_aliases

{

     die "Recursively expanding the expansion alias" if $in_exp++;

     my $cmdref = shift;

     my $exp_cnt = 0;

     while($cmdref =~ /^(\S+)/ and $DB::alias{$1})

     {

          my $i = $1;

          die "Alias expansion exceeds 100 iterations" if $exp_cnt++ > 100;

          my $cmd = $$cmdref;

          package DB;

          eval "\$cmd = $alias{$i}";

          die $@ if $@;

          $$cmdref = $cmd;

     }

     $in_exp--;

} ;

$DB::alias{exp} = '//; expand_db_aliases(\$cmd);';

The heavy lifting is done in the expand_db_aliases subroutine, which matches the actual instructions used by the debugger to expand aliases as closely as possible.

Loading your customizations automatically

If there is a file named ".perldb" in your home directory, the Perl debugger will load it and interpret its contents as Perl code after it initializes itself.  You can put any code-based customizations you desire into this file.  You can (and should) also use this file to load any dependencies required by your customizations.  For the replacement "x" command, I added the following to my .perldb file:

use Data::Dumper;

$DB::alias{x} = 's/xx\s+(.*)/p Data::Dumper::Dumper($1)/';

Determine a day's ordinal suffix: 1st, 2nd, 3rd, 4th, etc.

e.g. for dates you don't want to display "19 July" but rather "19th July":

my $ordinal;
if ($foo =~ /(?<!1)1$/) {
    $ordinal = 'st';
} elsif ($foo =~ /(?<!1)2$/) {
    $ordinal = 'nd';
} elsif ($foo =~ /(?<!1)3$/) {
    $ordinal = 'rd';
} else {
    $ordinal = 'th';
}

Bonus points if you can integrate this with DateTime's strftime() method neatly.

(source)

Lock rows with DBIx::Class

$schema->txn_do(sub{

    $foos_rs->search({}, {for => 'update'})->all; # Lock rows

    # Check status of something

    # Update it
});

(source, source, source)

Code works on one environment but not another

What can differ between environments? Check the following:

* Your code (obviously)
* Versions of other dependent packages - both in-house and third-party
* Versions of other installed in-house modules
* Versions of other Perl CPAN modules
* Processes which didn't die when you restarted the app
* Data in the database
* Number of rows in tables, i.e. is some limit being hit?
* Schema of the database
* Browser cache
* Server side web cache
* Files on disk, e.g. cached print documents

(source: a decade's experience building software)