Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
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 Perl.com use strict either. I wonder stance his new book will take.