dsimcha wrote: > == Quote from Lutger ([email protected])'s article ... >> int a = 1; >> int b = --a, ++a; >> assert(b == 1); >> assert(a == 1); > > Axe. Looks like the only things it's good for are making code undreadable > and abusing for loop syntax to... > > Make code unreadable. > > When the heck would this be significantly more readable, safer, or more > concise > than doing the equivalent without it? Also, from previous discussions I > vaguely remember it's constraining other parts of the syntax.
Those discussions were about nice native tuple syntax. The only argument in favor of the comma operator I can remember is code-generation.
