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
Alarm bells
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I, Heretic (Score:2)
I don't generally put -w in start-up line. I figure that the average runner of the tool isn't going to care enough to look up the warnings they get, and when I'm testing/debugging I run the script using "perl -w" anyway. It makes it easier with shell-history-substitution to add/subtract other flags like -d.
On the other hand, anything that is important enough to go from one-liner to actual script runs under strict, even if it's only 10-15 lines long.
--rjray
Re:I, Heretic (Score:1)
I don't generally put -w in start-up line.
Me too. I include 'use strict' in the smallest of scripts, but -w is bloody useless. 'perl -wc ' is great though. Screw runtime warnings.
OH PLEASE WARN ME ABOUT 'use of uninitialized value in concatentation (.)' AGAIN!
Re:I, Heretic (Score:2)
.=on an uninitialized variable. It happens, for example, when I interpolate an uninitialized variable into a string. Do you normally want to do that?Re:I, Heretic (Score:1)
yup. Most of the time, I don't care.
Reply to This
Parent