What do you want in the next C standard? For me it's namespaces, damn they make libraries simple.
Name:
Anonymous2009-11-10 22:18
To the people who said function overloading, namespaces, templates, containers, higher order functions, garbage collection, coroutines, I say: STFU. It's C. Don't try to turn C into C++ or worse. If you want namespaces, templates, and containers, just write C++... it supports all of those things, right now. If you don't like the overhead of exceptions then turn them off. What makes C useful is that it's good at its niche: systems programming, and writing low level code such as codecs. It's also a great target language for compilers... there are compilers for Lisp, Scheme, Haskell, Objective-C, C++, and more that all target C because C is so light-weight it's practically assembly. Lots of interpreters are written in C: Python, Ruby, Lua, and Perl come to mind. None of these would really benefit from the cruft listed above.
To the person who said closures: Yeah, I'd like that too. Apple did it, looks like it made it into clang and probably will come to GCC too.
My #1 wish for C1X is support for UTF-16 string literals. And guess what? I got my wish. (I read the C1X draft... u"some string" is UTF-16, U"some string" is UTF-32. sweet.)