I'm happy to revise my node so it explains things better.

You discuss "what is the prototype of a function after parsing" (that's knowable contrary to your claims) rather than "what will be the prototype of a function after parsing" (that's not knowable).

Or put differently, you talk about one instance of the parser when the problem is with differences in the output of different instances of the parser.

If there's a fallacy, it's assuming that the output of an instance of the parser will be the same as the output of another instance of the parser. That would be a very bad fallacy to make since that's the general hypothesis that needs proving or disproving.

In reply to Re^5: Perl is not Dynamically Parseable by ikegami
in thread Perl is not Dynamically Parseable by Jeffrey Kegler

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.