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.
  • A lot of systems today use one or more proxies around a number of objects to implement declarative transactions or other goodies. (Of course, these are much easier to implement in Perl or other dynamic languages, but that's another show.) So as a result you'll frequently have a number steps where each proxy intercepts the method, figures out what to dispatch it to, then invoke the relevant method using reflection.

    Fun when debugging, too...
    • Yes; I'm seeing a lot of those.

      There needs to be the equivalent of goto &NAME in Java.

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  • Yeah, I'm starting to boggle at the Java-length stacks I'm seeing from my code that uses both Moose and POE. Pages and pages long.
    --
    rjbs
    • That's 'cause stevan loves longmess apparently.

      As for Java, the call traces are deep because you see the call stack all the way down to "main". Try going 50 levels deep in a mod_perl app, then looking at the C stack in GDB. It's deep because you have Apache in there, then Perl, then Perl's management of your stack.
      • Be nice if he gave the user the choice. There’s always Carp::Always for those times you do need a full trace, and then you get one from any uncaught exceptions, not just those where the author coöperated. And the rest of the time, you can leave it out.