3 ms·
Even if one uses a tiny subset of C++, the new standard provides many improvements suited for nearly any subset. For instance: - Expected notation for angle br
by danieldk 16y ago
Even if one uses a tiny subset of C++, the new standard provides many improvements suited for nearly any subset. For instance:
- Expected notation for angle brackets (vector<vector<string>> versus vector<vector<string> >).
- Type inference using the 'auto' keyword.
- Initializer lists.
- Range-based loops.
- Strongly-typed enumerations.
- Delegation in constructors (constructor-constructor calls).
- Incorporation of TR1, which brings stuff like shared_ptr and containers based on hashing (unordered_map/unordered_set).
- cageface 16y agoType inference using the 'auto' keyword. This is the one I'm looking forward to. Maybe I won't have to typedef every stl container I use just to make my code readable.
- deleted 16y ago[deleted]
- rwmj 16y agoBut compared to real type inference? In languages which have been around since the early 80s?? Just being able to infer the type in the right side of an expression is rubbish.
- cageface 16y agoOf course, but I can't use any of those languages to implement commercial audio units so I'm happy to have something in the one language in which I can.
- rwmj 16y agoReally? You've actually (and verifiably) tried this or not?
- cageface 16y agoMaybe you've never written audio unit or vst plugins? This is a domain in which C++ virtual functions are considered too slow, not to mention things like garbage collection. There's a reason everybody writes this stuff in C++ (and often assembly).
- 16s 16y agoThe new unorder containers are very nice. They are containers based-on hash table data structures and are very fast for certain problems. It's nice to have them in the standard.