in reply to Re^18: Why is the execution order of subexpressions undefined?
in thread Why is the execution order of subexpressions undefined?

Helloooooo. Erlang variables are single assignment. That's the whole point.
  • Comment on Re^19: Why is the execution order of subexpressions undefined?

Replies are listed 'Best First'.
Re^20: Why is the execution order of subexpressions undefined?
by BrowserUk (Patriarch) on Apr 15, 2005 at 00:11 UTC

    And? I didn't suggest otherwise. I mention Erlang as a counter to the monads fudge of Haskell.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco.
    Rule 1 has a caveat! -- Who broke the cabal?
[reply]
[d/l]
      But that's the whole reason evaluation order doesn't matter in Erlang. And lack of that feature in Perl is exaclty the cause of all your problems.
[reply]
        But that's the whole reason evaluation order doesn't matter in Erlang.

        As I already pointed to the other anonymonk, I did not mention Erlang in that context. Only as a (preferable) altenative to Haskell, especially with regard to it's treatment of concurrency, so stop stating the obvious.

        And lack of that feature in Perl is exaclty the cause of all your problems.

        I don't have any problems. I never did. Read the title of the thread, I simply asked why.

        And so far, noone has offered a single good reason why EO should not be defined in Perl, nor countered my assertion that Perl does not benefit from it's being undefined in terms of efficiency, which is the only reason so far offered.

        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        Lingua non convalesco, consenesco et abolesco.
        Rule 1 has a caveat! -- Who broke the cabal?
[reply]

In Section Seekers of Perl Wisdom