Linked by David Adams on Sun 14th Aug 2011 22:41 UTC, submitted by subterrific
General Development The final ISO ballot on C++0x closed on Wednesday, and we just received the results: Unanimous approval. The next revision of C++ that we've been calling "C++0x" is now an International Standard! Geneva will take several months to publish it, but we hope it will be published well within the year, and then we'll be able to call it "C++11."
Thread beginning with comment 485038
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Yet another standard...
by moondevil on Mon 15th Aug 2011 10:19 UTC in reply to "RE[4]: Yet another standard..."
moondevil
Member since:
2005-07-08

Sure. they only want whats best for us.
Why use standard size-secure functions that are supported by world+dog when you can invent a completely incompatible C-runtime.
I assume that this is the first time you hear about EEE, right?


It is so incompatible that is part of the C standard process, ISO/IEC WDTR 24731, TR 24731-1.

http://www.open-std.org/jtc1/sc22/wg14/www/projects#24731

And was actually contributed to ISO by Microsoft.

Reply Parent Score: 2

RE[6]: Yet another standard...
by gilboa on Mon 15th Aug 2011 10:54 in reply to "RE[5]: Yet another standard..."
gilboa Member since:
2005-07-06

It is so incompatible that is part of the C standard process, ISO/IEC WDTR 24731, TR 24731-1.

http://www.open-std.org/jtc1/sc22/wg14/www/projects#24731

And was actually contributed to ISO by Microsoft.


I as unaware that _secure extensions were ISO'ed.
I concede the point. (Do I continue to claim that using MS CRT and CRT flags generated broken cross platform code, but that's anther argument)

- Gilboa

Reply Parent Score: 2