Don't take PBP as a set of laws.

PBP is a set of guidelines. And it isn't so much about what the rules say, the value of PBP lies in its motivation. I very much prefer to work with a programmer who has reasons to reject all the rules in PBP, then a programmer who can quote chapter and verse which rule(s) a particular statement of his follows, but only does so because PBP says so.

Clearly, if a following a rule from PBP breaks your code, and you have to do unnatural things to unbreak it, it's not a good idea to follow said rule.

If you have a function that is supposed to return in list context, a one element list with a false value (and you seem to have such a function), then "return undef" is perfectly reasonble.

In reply to Re: return explicit undef - Best Practices? by JavaFan
in thread return explicit undef - Best Practices? by Boldra

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.