Occasionally I find some useful tricks when programming stuff that can improve performance or otherwise enhance the resulting software. This thread will be used to collect assorted tips and tricks, and you can post your own interesting stuff here too. Today's tip: MSVC's cout is ridiculously slow. It turns out this is because MSVC doesn't normally buffer cout (and probably cerr) by default. Solution: Add this to the beginning of your program: Code (Text): if (setvbuf(stdout, 0, _IOLBF, 4096) != 0) { abort(); } if (setvbuf(stderr, 0, _IOLBF, 4096) != 0) { abort(); } This sets a 4K line buffer for both stdout and stderr. I ran the test program listed at the below MS Connect page, and found that on MSVC 2010, this improves printf() performance by around 1x-1.5x, and cout performance by over 30x. (MSVC 2013 performance with setvbuf() was slightly faster than MSVC 2010, but interestingly it was slower than 2010 if setvbuf() wasn't used.) (Reference: https://connect.microsoft.com/VisualStudio/feedback/details/642876/std-wcout-is-ten-times-slower-than-wprintf-performance-bug-in-c-library ) [NOTE: The referenced page also has a tip for using cout.pubsetbuf(), but on MSVC 2013 at least, if the buffer isn't flushed using endl, MSVCP120 may overflow the buffer, resulting in a crash. It doesn't improve performance that much compared to setvbuf() anyway, so don't bother using it.] I haven't tested mingw gcc or Linux gcc yet, but I would assume both of those properly buffer stdout and cout. (...actually, considering that's a property of the C library, it'd more appropriately be MSVCRT [which doesn't buffer stdout] and glibc [which might?].) EDIT: MSVC doesn't actually support line buffering. Enabling line buffering will actually enable full buffering, which may be problematic since printf() on MSVC 2010 doesn't seem to flush the buffer after a newline. endl does flush the buffer. If you're using printf, you can flush the buffer manually using fflush(stdout), but that isn't optimal.
In C++, you can get the number of elements in an array by using: Code (Text): template <typename T, size_t N> inline size_t LengthOfArray(const T(&)[N]) { return N; } Similarly, the total size of an array can be retrieved with: Code (Text): template <typename T, size_t N> inline size_t SizeOfArray(const T(&)[N]) { return N * sizeof(T); }
Is there any significant difference between this and sizeof(array)/sizeof(array[0])? Code (Text): #include <stdio.h> template <typename T, size_t N> inline size_t LengthOfArray(const T(&)[N]) { return N; } size_t pointer_sizeof(int array[]) { return sizeof(array)/sizeof(array[0]); } #if 0 // doesn't compile: no matching function for call to 'LengthOfArray(int*&)' size_t pointer_template(int array[]) { return LengthOfArray(array); } #endif int main(void) { int array[1000]; printf("%u\n", sizeof(array)/sizeof(array[0])); printf("%u\n", LengthOfArray(array)); printf("%u\n", pointer_sizeof(array)); // printf("%zu\n", pointer_template(array)); return 0; } gives: 1000 1000 1 I suppose it has the benefit of type checking, but sizeof works in straight C too.
The only difference is type checking, it prevents accidentally converting an array to a pointer as in your pointer_sizeof function.
If you're using C++11, look into shared_ptr. It can very verbose in terms of code, but pretty handy in the right situation. Making a game and you need to detect collisions between a lot of objects? Use quadtrees. A better random number generator for C++: here. Here's one from me: Line of sight testing in a 2D tile based game. (Let me know if there's any errors with this one, please)
I use shared_ptr to manage a block of data allocated by a class' initializer in the SADX Mod Loader, so it gets deleted automatically when the last instance of the object does. It's not ideal, since other code could hold pointers into the block of data when the object is deleted, but I think it's better than requiring the client to manually delete the data.
Today's tip: Don't pass std::string (or any other large object) by value. Code (Text): int someFunction(std::string x) { // blah } If your function doesn't modify the string, then it's better to pass it by const reference. gcc uses copy-on-write strings, so it has to increment a reference counter every time you pass a string by value. MSVC, on the other hand, uses "short strings", which requires copying at least 28 bytes (32-bit) or 40 bytes (64-bit) every time you pass a string by value. This isn't including the string data itself, which is either stored within the string object if it's 15 bytes or less, or allocated separately on the heap if it's larger than 16 bytes. Do this instead: Code (Text): int someFunction(const std::string &x) { // blah } This is effectively passing a const pointer that works the same way as a regular object. Supposedly C++ 2011 eliminates the need for passing by const reference by using "move semantics", but it hasn't been adopted much outside of e.g. libstdc++ and boost. I'd recommend using const reference anyway, since it also prevents accidental string overwrites.
