comment on

Hi Gabor

The monastery's authority for such questions is dave_the_m and IIRC we already briefly talked about introspection here.

Regarding a (robust) API:

IIRC this is depending on the version of Perl, early versions compiled code into the function block to expand @_, later versions had dedicated OP-Codes for that. ( I could dig up that info from emails, if Dave doesn't show up)

so this could either boil down to inspecting the OP-Tree with B::Concise or calling a method from B (on a B::CV node most likely)

In any case, B::Deparse is written in Perl, so you can always look into it and diff different versions to locate how the info is extracted.

Whatever the result it would be nice if such an API was added to Sub::Util when it's not experimental anymore.

HTH :)

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

PS: This message will self-implode ASA Dave shows up ;-)

In reply to Re: Introspecting function signatures by LanX
in thread Introspecting function signatures by szabgab

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks