With reguards to your first technical note,
I didn't specify which two items formed "both". I was refering to perlfunc. :p
And yes, it's wrong.
It's not wrong because eval doesn't return undef on error.
It's wrong because eval doesn't always return undef on error, and there's no mention of that.

With reguards to your second technical note,
"eval returns an empty list" meant
"eval called return with an empty argument list", and
"An empty list is interpreted as undef in scalar context." meant
"return interprets an empty argument list as undef in scalar context."
My statements might have been vague where it didn't matter, but they weren't wrong.

Update: Expanded a bit

In reply to Re^7: Blessing interior hashes by ikegami
in thread Blessing interior hashes by throop

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.