Usually I just take these cool questions as a chance to learn more. I scanned your link to perlmod (UNITCHECK), something about the fact that it's processed LIFO (outside of execution) and other things (INIT, e.g.) are processed FIFO (during execution) makes me think that AUTOLOAD might not be your only potential gap.

What problem are you trying to solve? Implementing things like variable scope awareness and caller information in the IDE by dumping some semi-static (I pause at calling it fully dynamic, perhaps out of ignorance) info produced by pre-execution phases of perl itself?

In reply to Re: Storing dynamic parse results for static introspection? by perlfan
in thread Storing dynamic parse results for static introspection? by LanX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.