46 replies to this topic

[3DModelerMan]

What are your favorite features of C++ or the C++ standard library? Useful features that are sort of obscure, or that you haven't seen being used very much. I think I would go with member function pointers.

[frob]

I'd suggest the majority of the standard library is underused.
I'd further suggest that good portions of the standard library is of little use to games development.

/edit:

For underuse examples, most people will write their own simple functions rather than relying on the algorithm library. Some of the ordering and searching functions are used occasionally, but few people will use std::transform(), std::generate() when they need to come up with a bunch of items. I've seen programmers run full sorts rather than functions like stable_partition() or partial_sort() when they need just a few items. And almost nobody normally uses the heap functionality, even though it can be a very solid alternative to sorted containers, especially when it comes to bulk changes.

For not applicable functionality examples, the entire Localization library of the C++ standard library is difficult to apply to game development; it doesn't play nice with the major game development localization tools. The Diagnostics library is of limited use -- most games implement their own custom asserts, warnings, and such, and many game companies have exceptions disabled for better or worse. RNG in the standard library is not sufficient for games. Most of the IO libraries are useless for games because they are blocking. Etc.

Edited by frob, 22 October 2012 - 06:01 PM.

[hupsilardee]

Yeah I first learned about member function pointers when I started using wxWidgets.
operator() is pretty cool too.

[patrrr]

That you can read and write from different elements in a union if the elements are structs and have the same prefix structure:

union {
   struct {int x, y; };
   struct {int u, v; };
}

x = 45;
cout << u;

I also like that the library and language is designed in such a way that the compilers can optimize usage of the library really well; gcc can optimize through almost everything in there.

Edited by patrrr, 23 October 2012 - 01:55 AM.

[iMalc]

I would have to say valarray.
It's potentially very relevant to games development too, yet I've never heard of its actual use anywhere.

[doeme]

I personally love quite a bit of the newish C++11 functionality, which is still not used by a lot of C++ developers I know, simply because they do not know of the existence of said features and because not all the features are supported by all the compilers.
Especially std::function, auto built-in smart-pointers are some of my new friends

I think a lot of features are just not known to many developers and the STL contains a huge load of stuff that comes in very handy quite often, but one has to know that it is there in the first place

Edited by doeme, 23 October 2012 - 08:02 AM.

[Kyall]

variable arguments
...
^ is awesome

[Servant of the Lord]

RNG in the standard library is not sufficient for games.

Just FYI, there is a better RNG in the standard library for C++11 (Also higher-accuracy cross-platform timers).
C++11, while mostly focused on improving the core language (which it did), does add a few things of interest to the standard library that will help game developers moving forward (such as easier multithreading and the TR1-promoted smart pointers).

I'm personally trying to learn the algorithms that have always been in C++, since I've not much experience in them; later I'd love to learn the proper usage of streams.

[demonkoryu]

later I'd love to learn the proper usage of streams.

If you mean iostreams... i advise to skip those. They're not asynchronous (if you're using file streams), they're internally complex with many trippings for you to discover (even ignoring threading issues); you're gonna have problems with I18N (you can't use the format string as a resource, as is possible with [possibly positional] printf parameters), it's more cumbersome to read/write formatting specifications and so on...

[Bregma]

Lambdas have suddenly (well, relatively speaking, given the glacial pace of standards development) made <algorithm> incredibly useful. I like lambdas + <algorithm>. The <random> library is a gollysend: generative environments that used to take hundreds of lines of code can be condensed down to a few dozen. std::function and std::bind working together make decoupling clear and maintainable. Uniform initialization is wonderful. Ya know, C++11 is just chock full of really, really useful stuff.

[Evil Steve]

Personally I like dropping the comma operator into functions just to upset people who have to read my code.

[3DModelerMan]

Personally I like dropping the comma operator into functions just to upset people who have to read my code.

You are Evil Steve

[Geometrian]

Duff's device: not exceptionally useful, but clever.

[adeyblue]

std::get_temporary_buffer & std::return_temporary_buffer.
I am convined nobody has ever used these functions for anything, ever.

[Washu]

That you can read and write from different elements in a union if the elements are structs and have the same prefix structure:

union {
   struct {int x, y; };
   struct {int u, v; };
}

x = 45;
cout << u;

I also like that the library and language is designed in such a way that the compilers can optimize usage of the library really well; gcc can optimize through almost everything in there.

structures declared within an anonymous union are not legal C++. Its a visual studio extension.

-changed wording slightly

Edited by Washu, 23 October 2012 - 02:10 PM.

[patrrr]

anonymous structures within an anonymous union are not legal C++. Its a visual studio extension.

Crap, I've been looking the standard up and down and I didn't find anything that would make this illegal. Though I could've looked harder. Maybe there's a difference between C11 and C++11 in this regard? But I do know that it's not just a visual studio extension; it works well on gcc and clang as well.

[nox_pp]

Variadic templates are ridiculously powerful, and antiquate a lot of redundant C++03 template metaprogramming.

Initializer lists are a much needed addition to the language. They add the ability to make classes feel more like POD's, even when they aren't.

std::vector<int> ivec = {1, 2, 3, 4};
//vs.
std::vector<int> ivec;
ivec.push_back(1);
ivec.push_back(2);
ivec.push_back(3);
ivec.push_back(4);

[Washu]

anonymous structures within an anonymous union are not legal C++. Its a visual studio extension.

Crap, I've been looking the standard up and down and I didn't find anything that would make this illegal. Though I could've looked harder. Maybe there's a difference between C11 and C++11 in this regard? But I do know that it's not just a visual studio extension; it works well on gcc and clang as well.

C++98 - §9.5.2
[Note: nested types and functions cannot be declared within an anonymous union.]

C++11 - §9.5.5
[ Note: Nested types and functions cannot be declared within an anonymous union. —end note ]

Edited by Washu, 23 October 2012 - 01:55 PM.

[joew]

Out of curiosity I'm guessing it was left out of the C++11 standard do to ambiguous naming as functions/variables would live in an unnamed inner scope?

[Washu]

Out of curiosity I'm guessing it was left out of the C++11 standard do to ambiguous naming as functions/variables would live in an unnamed inner scope?

In the anonymous case:

void f() {
	union {
		struct { int x, y; };
		struct { int x, y; };
	} u;
}

In the not so anonymous case its harder to come up with the same example, but there are similar issues.

I should note that the only places I've actually seen people use anonymous unions/structures was usually almost always a hack that could have been avoided.

Edited by Washu, 23 October 2012 - 02:15 PM.