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

use Perl Log In

Log In

[ Create a new account ]

chaoticset (2105)

chaoticset
  (email not shown publicly)
http://chaoticset.perlmonk.org/
AOL IM: chaoticset23 (Add Buddy, Send Message)
Yahoo! ID: illuminatus_foil (Add User, Send Message)

JAPH. (That's right -- I'm not Really Inexperienced any more.)

I'm not just here, I'm here [perlmonks.org], and here [javajunkies.org] too, I ramble randomly in my philosophical blog [blogspot.com] and my other blog [blogspot.com]. Soon I'll come in a convenient six-pack.

Journal of chaoticset (2105)

Monday February 23, 2004
11:46 AM

Debugging GONE WILD

[ #17572 ]
Wasn't a bug.

A single print statement inserted in the sub wasn't printing to STDOUT, and there was no error, etc., but in debug all of it showed up. I think Net::AIM is somehow suppressing STDOUT in subroutines called as handlers, because the sub is being executed without -d, it's just that the strings aren't being printed to STDOUT. Ah well. If I need 'em that bad, I'll run it in debug.

Now, on to the rest of the actual work. I can't help but feel sheepish -- I've spent a buttload of time working on a non-bug. I squished something that wasn't even a cucharacha, and it took me a long time to do it. :(

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.