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.
  • First of all, “Devel::” is reserved for things to be loaded using perl’s -d flag. (It should have been a more specific namespace, really, so people wouldn’t be tempted to dump random junk in there that has nothing to do with -d, maybe DB::Custom:: or something.)

    Also, “Devel::Recreate” gives no indication whatsoever about what it recreates. That would be a package, which suggests that the right TLNS for your module is “Package::”.

    Now, what does it do with a

    • I knew I could count on you to smack me around. Thanks :)

      • Oh dear, on re-read, that comment sounds a little more vigorous than I intended. :-) Sorry. Wasn’t meant to be slap-around. I know most people find naming much harder and more tedious than I do.

    • Maybe, Package::OpCodeDumper?

      Then again, it isn't the opcodes, at least from my weak grasp of the internals, is it?
      • Nope. Not trying to dump opcodes, though I may be forced to dig into them at some point. Just trying to dump what perl thinks the source code looks like.

        • Isn't this about dumping how much of the module exists when it dies during load? Seems like caller() from a $SIG{__DIE__} hook and a line number would suffice. What am I missing? Are you trying to get valid perl output, or just information?

          To really do it right, I think you end up source filtering (PPI?) everything (unshift(@INC, sub {...})) into s-expressions or something. I've always wished perl were more introspective, but it seems like syntax is the enemy of introspection (and I really like syntax,