in reply to Re^21: printing unitialized value of the 'do BLOCK' (EXPRESSION vs TERM vs STATEMENT)
in thread printing unitialized value of the 'do BLOCK'

It's all covered by my initial post. It explains that the documentation doesn't define what happens and that it could be implied that it's Undefined Behaviour, it explains what usually happens, and it explains that you can't always count on it happening (in the form of a link to a reply that provides an example where it doesn't happen).

  • Comment on Re^22: printing unitialized value of the 'do BLOCK' (EXPRESSION vs TERM vs STATEMENT)

Replies are listed 'Best First'.
Re^23: printing unitialized value of the 'do BLOCK' (EXPRESSION vs TERM vs STATEMENT)
by LanX (Saint) on Jan 02, 2020 at 13:30 UTC
    Thanks.

    I consider the now fixed unless (1) case a bug derived from improper constant folding optimization.

    Regarding "undefined behavior" I'd rather say "poorly documented behavior".

    Returning the result of the last statement is very normal in Lisp ( which has no return or any other jump directive in core).

    Larry was repeatedly very supportive for Lisp constructs, at one "State of the Onion" he even criticized Python for neglecting them.

    Given that people are actively using this behavior in productive code for over 20 years already, we should rather try to document and test it properly.

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom