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
cog (4665)
cog
{cog} {at} {cpan.org}
http://jose-castro.org/
Yahoo! ID: jose_alves_castro (Add User, Send Message)
Internacional Man of Mystery.
{cog} {at} {cpan.org}
http://jose-castro.org/
Yahoo! ID: jose_alves_castro (Add User, Send Message)
Internacional Man of Mystery.
Tuesday February 15, 2005
12:59 PM
Print your debug information on STDERR
One thing I do from time to time is to open a file to write to it in the STDOUT filehandle... (and I am also known for reading a file via STDIN)
This saves me the time (and keystrokes) of using a filehandle name (or even picking one up).
Today, for the first time ever, this caused me a bug (fortunately, it only took me about 10 minutes to figure out what was happening)... you see, I was printing debugging information which was screwing up the output file...
Always remember, print your debug information on STDERR at all times
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Save Keystrokes! (Score:1)
Save time and spell it warn.
Wrong solution :) (Score:1)
the correct solution is always, *always* use Log::Log4perl.
By default, it does what you want, and eventually, when you really need it, it will do it also, whatever it is...
Clear as mud, I hope...
life is short