Youre mission: Free the C standard committee

From the ENTERPRISERS and the Microsofts
Examples of them being hurt/harmful: C11 Annex K (bad copy-paste of MS's "safe" functions, see http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1118.htm), C11 Threads and atomics, the C11 aligned_alloc function is made to match MS's one, etc

>>1
The _s family of functions is a travesty on so many levels. Their sole proponent, Microsoft, doesn't even implement them as specified by the standard!

Just compare the behavior described at http://msdn.microsoft.com/en-us/library/8ef0s5kh.aspx to TR 24731 - in order to achieve behavior resembling the standard, anyone using Microsoft's C runtime library must call a Microsoft specific function, _set_invalid_parameter_handler, and register a do-nothing function to allow invocations of _s functions to return without killing the whole program. Why Microsoft would push to get this garbage of theirs standardized and then ignore the standard is beyond me.

>>1
Relax. No one but Microsoft will ever implement the so called safe functions library. Everyone knows it's bullshit except Microsoft-loving plebs who honestly believe it makes their programs more safe. Microsoft doesn't even implement their own shit properly, they kept all identifiers prefixed with "_" even though it's a standard now.

After all, Microsoft doesn't care, it's a soulless corporation filled with beta nerds just trying to make a dollar off the rotting corpse of the dead giant, and indian programmers who used to shit in the streets when they were growing up.

The C11 threads and atomics library is okay, although the threads library could use an extra few features, and perhaps expose one additional primitive to make writing atomic data-structures more efficient: the event-count. Other than that, it's a subset of pthreads.