News for hackers. Stuff that matters.
Re:The Crack Programming Language by perfunctory on Monday November 26, 2012 @03:08AM (#4831123)
I am inclined to dismiss the language for this:

  i++
Re:The Crack Programming Language by wbhart on Monday November 26, 2012 @08:50AM (#4831881)
I would have once disagreed with you being a C programmer. However, nowadays there is a tendency to providing functional features, including for example if..else expressions. But if you make i++ an expression, you end up with ambiguities if i++ ends up being the last line of an if..else branch, and say s = "hello" being the last line of the other branch. In a statically compiled language, the compiler has no choice but to interpret both as expressions and complain about the types of the two if..else branch expressions not matching. However, the programmer may have intended these expressions for their side effects only, not their values. Perfectly good code needs to be rewritten to work around the type checker. How fiddly.
Re:The Crack Programming Language by derleth on Monday November 26, 2012 @03:37AM (#4831170)
Why?
Re:The Crack Programming Language by mguillemot on Monday November 26, 2012 @04:40AM (#4831297)
I'd venture into guessing that the parent reason is that ++ and -- operators tend to make easy to bury side-effects where they're not obvious, like in the provided code sample:

__raw[args[i++]] = 1;

(C programmers would disagree about this, of course :) )