It is, in spirit, much more like eval, only that the evaluated code resides in a file, not in a string or block

The reason for requiring for avoiding undef has nothing to do with the purpose of function, so this doesn't matter.

We wouldn't place the requirment, that code evaluated by eval should return a true value unless it fails, do we?

What does matter is the interface provided by the functions. eval has a different interface, so it really doesn't matter what you do with eval. However, it is indeed quite common to have eval's body return true. 

my $foo = eval ...
    or die("...: $@");

[download]

In reply to Re^7: Why do we need a \n with do FILENAME? by ikegami
in thread Why do we need a \n with do FILENAME? by rovf

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.