s/require/use/g or move the 'require' outside of the eval and you'll get more of what you expected. BAREWORD only turns into a call to the BAREWORD subroutine if the subroutine is defined when the BAREWORD code is compiled. In your examples, the require and BAREWORD statements are compiled first, then the require is run (which finally defines the BAREWORD() subroutine) -- so the subroutine isn't defined when the BAREWORD statement is compiled.

Update: And if you want it to complain about barewords, then you need to use strict.

                - tye

In reply to Re: runtime eval() and constants (order) by tye
in thread runtime eval() and constants by dpmott

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.