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.
  • Sometimes you get a little loopy after staring at the debugger for a long time (2+ years to write most of that documentation).

    I can't claim credit for the "unreadable code" one though. That was an original, dating back to very close to the debugger's inception.

    I'm glad you noticed. I was wondering if anyone would ever actually look at all that work...
  • Isn't MJD taking a whack at a rewrite of the debugger?
    --
    The great thing about multitasking is that several things can go wrong at once.
    • As far as I know, yes. Don't know how far he's gotten. I think Higher-Order Perl (and being a dad) may have taken up most of his cycles up till now.

      For entertainment, look at DB.pm in any recent Perl distribution. Interesting, innit? Sarathy actually put that together a long time ago, and wrote a proof-of-concept debugger called SWAT that used it. If you're interested, I can track down the SWAT source for you.
    • Somehow obra convinced me to have a go at a new debugger. Devel::ebug [cpan.org] is the result so far. "Devel::ebug is a work in progress."
  • # Yes, go down a level.
    local $level = $level + 1;
  • # The following code may be executed now:
    # BEGIN {warn 4}
    Well, better 4 warned...
    --
    rjbs