Actually, the order in which function arguments are evaluated is undefined. http://c-faq.com/expr/comma.html
You can use a comma in other expressions to introduce a sequence point: http://c-faq.com/~scs/cgi-bin/faqcat.cgi?sec=expr#seqpoints
Thanks for your clever comment and for those emitting similar concerns.
You surely are right. I wanted to give a quick example, turns out it was a bad one. Next time I'll write :
int i = 0;
printf("%i", i++); // prints 0
printf("%i", ++i); // prints 2turns out it was a bad one
Given that you were making a point on an article about the complexity of C, I'd say it was an unintentionally excellent example.
Re:The Little C Function From Hell
by sirclueless on Tuesday June 19, 2012 @03:02PM
(#4133542)
If you really want to make your brain hurt, there was an article on HN a while ago about the following statement:
i = i++;
Evaluating that expression takes a real dive into the guts of the C spec.I believe you trigger an undefined behaviour there. You modify i twice in the same statement.
Re:The Little C Function From Hell
by jim_kaiser on Tuesday June 19, 2012 @12:45PM
(#4132756)
The standard says, evaluation order of function arguments is undefined.. but in general, printf evaluates right to left. This was a common puzzle as I remember.
[EDIT] Turns out this is a bad example, as "the order in which function arguments are evaluated is undefined" (cf. below) Correct is :