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.

Why would you ever make a non-parametric function modify some kind of counter variable?

Stop trying to market Haskell with your synthetic ``human errors'' that never actually happen to anyone with a brain. Haskell can't magically fix stupid and all your scenarios have been a severe case of stupid. This is ``put braces around one-liner ifs'' all over again.

I have C's order of operations tattooed on my right arm.

Problem solved.

Don't use global variables, Ahmed

>>4

This is C. No rules. You can use everything, including goto.