Aragorn's Journal
http://use.perl.org/~Aragorn/journal/
Aragorn's use Perl Journalen-ususe Perl; is Copyright 1998-2006, Chris Nandor. Stories, comments, journals, and other submissions posted on use Perl; are Copyright their respective owners.2012-01-25T02:39:14+00:00pudgepudge@perl.orgTechnologyhourly11970-01-01T00:00+00:00Aragorn's Journalhttp://use.perl.org/images/topics/useperl.gif
http://use.perl.org/~Aragorn/journal/
Giving talks
http://use.perl.org/~Aragorn/journal/28940?from=rss
<p>Last Tuesday I gave my first talk at the <a href="http://amsterdam.pm.org/">Amsterdam Perl Mongers</a>' meeting. I did an introduction to <a href="http://search.cpan.org/~adamk/PPI-1.110/">PPI</a>, <a href="http://use.perl.org/~Alias/">Adam Kennedy</a>'s Perl parser
module. It was my first real talk, but once I got started, it went reasonably
well, I think. People were interested in the topic, and some nice discussion
was had.
</p><p>The organizer of the <a href="http://workshop.perlpromo.nl/">Dutch Perl Workshop</a> asked me to do the talk at the workshop. Apparently an uncertain "Uhhh" is equivalent to "Yes, of course!" as the next day, I saw name added to the listof speakers. I'm flattered<nobr> <wbr></nobr>:-)
</p>Aragorn2006-03-09T20:06:30+00:00journalPro Perl Debugging
http://use.perl.org/~Aragorn/journal/28463?from=rss
<p>
This morning I finished reading the book "Pro Perl Debugging", by
Richard Foley. It's a missed chance. The topic of using the Perl
debugger is an interesting one, and the basic information on using it is sound. Unfortunately, the book is absolutely <em>riddled</em> with presentational errors. From wrong fonts to mismatches in the initial code listings, and the code which is seen in the debugging
walkthrough.
</p><p>
Some examples:
</p><p>
In listing 4-1, a program is presented which contains a bug.
Unfortunately, the buggy program contains a bug:
</p><p>
Line 9 in the listing says: <code>my $regex = $ENV{REGEX} || '[\$\@\%\*]]+';</code>
But in the walkthrough, line 9 suddenly is <code>my $regex = $ENV{REGEX} || '[\$\@\%\*]&+';</code>. See the difference?
</p><p>
In chapter 11, debugging regular expressions is discussed. A common abbreviation of "regular expression" is "regex". But why is "regex" printed in a monospaced font? Totally unnecessary.
</p><p>
When showing a transcript of something you do on the command-line, be sure that the command-line shown is actually what produces the subsequent output:</p><blockquote><div><p> <tt>perldb -Dr -e '"spott" =~<nobr> <wbr></nobr>/spot/'<br>[line snipped]<br>Guessing start of match, REx 'spot' against 'sxpott'...</tt></p></div> </blockquote><p>
I think the extra costs of have the book have a hardcover could have been spent better on technical review and editing.
</p>Aragorn2006-01-25T10:42:29+00:00journalNew Year's resolutions
http://use.perl.org/~Aragorn/journal/28195?from=rss
This being my first journal entry on <a href="http://use.perl.org/">use.perl</a>, it's a good place to put some of my (Perl related) resolutions for 2006:
<ul>
<li>Write more modules and put them on CPAN</li><li>Keep a regular blog on my Perl stuff here</li><li>Do some talks for the <a href="http://amsterdam.pm.org/">Amsterdam Perl Mongers</a> </li><li>Study <a href="http://hop.perl.plover.com/">Higher Order Perl</a> </li></ul><p>
I do have some other things I want to get done in 2006, like losing 25kg of weight, read more books, watch less TV, but the above are at least on-topic here<nobr> <wbr></nobr>:-) Right now, I'll have to get rid of this damn cold.
</p><p>
Have a good 2006!</p>Aragorn2006-01-01T21:21:47+00:00journal