Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

  (email not shown publicly)
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Saturday May 14, 2005
10:49 PM

HOP Woes

[ #24695 ]

HOP is a wonderful book. However, what's not wonderful about the book is the lack of strict. I just spent 3 hours trying to track down a problem when I remembered that the code didn't use strict. Two seconds later, I found my bug. Grr ...

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Mark and I got in to a heated debate about this on his perl-quiz list a few years ago. Mark doesn't like how many of us tell new Perl programmers to 'use strict' almost like a Mantra and has a lightning talk based on it. We have since agreed to disagree.

    While this error you've spotted is possibly a typo, that wasn't in Mark's original code, to me it highlights why use strict and warnings are such useful things to include in your programs.

    • Not only do I tell newbies to "use strict", I also tell them to "use warnings" as well. I personally believe that if something doesn't pass "use strict" (without good reason), it shouldn't be in release code. HOP is a good book and has me thinking about Perl in different ways.
  • Mark is not a fan of strictures for some bewildering reason. None of the program repair shop articles at use strict either. I wonder stance his new book will take.