in reply to Re^11: Short-circuiting a map list. (This works! But ...)
in thread Short-circuiting a map list.

It is only applied to the "last statement of a subroutine". Not to the last statement of a do block?

The line you read may only have been talking about the last statement of a subroutine, but it applies for the last statement do blocks and everywhere else a return value is needed from a loop. You've even demonstrated this yourself.

But suddenly, you read a bit of the documentation, apply it to the wrong circumstance, assume that your misinterpretation is the only interpretation.

Actually, you're the one who is being a slave to the documentation, not listening to anything else.

And I'm pretty damn confident that I could find numerous examples of you using, and recommending the use, of the return value from a block.

Straw man. It's the return value of loops that's not defined, not blocks. eval and do aren't loops.

Replies are listed 'Best First'.
Re^13: Short-circuiting a map list. (This works! But ...)
by BrowserUk (Patriarch) on Oct 10, 2011 at 02:09 UTC

    I recently suggested conversation with you was like that with a goldfish, but that doesn't do it justice.

    You use a quote from the documentation in support of your misinterpretation.

    I counter, by putting that quote in its rightful context, and highlight your misinterpretation. I then quote another passage from the document you quoted that contradicts your quote (and also happens to support my argument), and then suggest that the implementation is the final arbiter.

    And your response is to ignore all that, and suggest that I am a slave to the documentation.

    Q: How many surrealists does it take to screw in a lightbulb?

    A: Fish.

    Bored now. Just stop.

      You presumed too much if that's what you think.

        Presume? Que? Fish!

        Just stop.