note
rjray
<p>Let's see-- excluding pragmata, but allowing references to
core modules, and not being cheesy and referencing any of my
own CPAN modules:</p>
<ol>
<li><b>Data::Dumper</b> - So useful in debugging, I've set
my <tt>PERL5DB</tt> environment variable to be,
"<tt>BEGIN&nbsp;{&nbsp;use&nbsp;Data::Dumper;&nbsp;require&nbsp;'perl5db.pl';&nbsp;}</tt>".</li>
<li>[cpan://SOAP::Lite] - Using it more and more each day</li>
<li>[cpan://HTTP::Daemon] - I've lost count of how many applications I've written that use this for their network layer</li>
<li>[http://www.gtkperl.org|Perl/GTK+ bindings] - if only the code were as stable as Perl/Tk</li>
<li>[http://perl.apache.org|mod_perl] - I'm always learning some new trick I can do with this one</li>
<li><b>B::Terse</b> - the opcode tree has proven indispensible when debugging core-dumps inside XS code</li>
<li>[cpan://XML::SAX] - starting to use this more and more</li>
<li>[cpan://Devel::Peek] - another indispensible tool for the XS programmer</li>
<li><b>AutoLoader</b> - dynamic loading for Perl code is good, especially when your (legacy) library has 30+ functions</li>
<li>[cpan://Image::Size] - OK, I'm cheating here. But I do a lot of HTML authoring for a local hobby club's website, and getting the image dimensions in a cut-and-paste form is very handy and very time-saving</li>
</ol>
<p>The ones that aren't linked are core modules, and you should be able
to find their manual pages here or on your Perl installation.
And yes, <b>Image::Size</b> is one of mine, but it really is
one of my most-used pieces of code. And it was my very first
CPAN submission, so I have a fondness for it.</p>
<p><i>--rjray</i></p>
150727
150727