in reply to Storing dynamic parse results for static introspection?

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?

Replies are listed 'Best First'.
Re^2: Storing dynamic parse results for static introspection?
by LanX (Saint) on Jul 21, 2020 at 17:55 UTC
    > Implementing things like ...

    Yes, things like that ...

    The most common complaint about inability to parse Perl statically is that prototypes of imported subs are unknown and that they change the way the source is parsed.

    (Most) imports happen at compile time and are known in the CHECK phase after the code was parsed and compiled.

    > these cool questions

    FWIW: I originally posted this as meditation, it was moved afterwards.

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery

[reply]

In Section Seekers of Perl Wisdom