Even if it doesn't, it's still unspecified for if statements as they aren't expressions either.

... if statements ... aren't expressions ...

if statements aren't expressions, but an
    if (CONDITION) { ... }
statement must evaluate the  CONDITION expression, and if that's the last expression evaluated in a subroutine (because it evaluates false), I thought that's what must be returned. At least, whenever I've encountered this situation, that's the way it's worked. (I don't like implicit returns myself and never use them, but just sayin' ...) I'd be interested to learn more about this.

---

Give a man a fish:  <%-{-{-{-<

Yes, that appears to be what's happening:

C:>perl -le "sub u { unless(shift) { 'false' } }; print u($_) for unde
+f, '', 0..3"
false
false
false
1
2
3

C:>perl -le "sub i { if(shift) { 'true' } }; print i($_) for undef, ''
+, 0..3"


0
true
true
true
[download]

I'm not sure if it's meeting the technical definition of "expression" from "If no return is found and if the last statement is an expression, its value is returned"... but the last statement executed was the failed if or unless, and as part of that execution of that statement, the CONDITIONAL expression had to be evaluated, so I can definitely see a good case for why that EXPR's value is what is returned. But since I couldn't find a perl-specific definition of "expression" (and it appears it's been a longstanding lack of definition, because as far back as 2001, people were asking What is the difference between a Statement and an Expression? without getting a canonical answer from the perl documents), there is wiggle-room in the interpretation of whether the documents claim the return value is unspecified or not.

Interesting sub-discussion. Thanks!