>>21
Char is defined as the smallest non-bitfield type available. If you were to suddenly redefine it as 32-bit unicode (
wchar_t ahoy!), you'd break lots of shit. If Java or C# is what you want, go use Java or C#. Even in those you have to mind your Unicode combining characters etc, so a char may not represent a single character by itself after all...
Complex types on the other hand are something that many HPC-oriented compilers have supported for a while, all in their mildly incompatible forms. It's something they basically had to standardize.
I will grant you that they could've finally excised
gets() from the standard library. But other than that and perhaps
strtok(), shit, I don't see how the C standard library is so bad.
Perhaps you just need to get yourself a proper utility library if you're looking to do application development; I'd recommend the GTK utility library, glib, if you can stomach the way it allocates tiny little bits of memory for rb-tree nodes and follows an overly verbose
g_function_naming_policy(). On the plus side, glib's got unicode handling functions that don't suck seven kinds of ass!