Evaluation Order Sucks

Just fixed an error with
array[count++]= foo();
where foo() modified count, in effect writing stuff into the incorrect location.

Haskell's lazy evaluation would have prevented that.

>>2

``human errors'' that never actually happen to anyone with a brain

There's nothing synthetic about it. >>1 may be full of shit, but so are you. Much of the software we all rely on is written by the brainless, to put it your way. The problem can be reliably solved with the appropriate aliasing semantics. They also provide thread safety.