Of course, the important stuff is there. People care about "static inline", member/array initializers, "long long", and "restrict". Nobody gives a damn about wchar_t unless they were duped into using it the first time around.
C1x
Thread local variables are handy and the _Atomic type qualifier might be useful too.
I'm all for standardizing (what are currently) compiler extensions to C - people probably won't abuse these features, it just avoids some platform specific code.
Out of the C99 add-ons I use only the long longs, Sepples comments, macros of variable arity, and variable-length arrays, and I don't feel like using an incomplete language just to have these.
Name:
Anonymous2010-08-29 11:04
C99, because why would I want to declare my variables at the start of every scope?
Though lately I've been using cl.exe so I was restricted to whatever standard of C that uses.
>>19 C99, because why would I want to declare my variables at the start of every scope?
So you can keep better track of the stack, instead of littering your code with random variables like some PHP skiddy.
>>27 i != 100;
I don't think you're even a programmer!
Name:
Anonymous2010-08-29 17:05
>>29
Your homework for tonight is to compile it and write a one page essay on how the not-equals operator has increased staff synergy and leveraged industry best practices at software startups using Java and VB.NET.
>>34 implying anyone on /prog/ still has an intact anus.
Name:
Anonymous2010-08-29 18:56
While we're on this topic, I kindly request the EXPERT C denizens of /prog/ to explain this bullshit[1]: (double (^)(int , long long))foo
``cast foo into block(int, long long) returning double''