Affective C++

The authoritative guide for High Quality C++!

(Warning: These are all jokes.)

[Affective C++ @AffectiveCpp]

@OmerFarukDinder (Just in case someone missed the point: @AffectiveCpp is a humorous account, everything we post is spectacularly wrong.)

[cts🌸 @gf_256]

On x86, the stack grows “down” towards lower addresses. However, this is only true in the northern hemisphere due to the Coriolis effect. In Australia, the stack grows up actually. That’s because they are all looking at their monitors upside down to avoid falling off the planet.

[Affective C++ @AffectiveCpp]

@tvaneerd @JamesMcNellis 🤔

[Affective C++ @AffectiveCpp]

@PeterSommerlad @isocpp Seems to be written by @Code_Analysis, I was previously unaware of him. Good article!

[Affective C++ @AffectiveCpp]

Don't do this manually of course, use something like CMake's target_odr_header(<target> ORIGINAL_HEADER_FILE_NAME NUMBER_OF_COPIES)

[Affective C++ @AffectiveCpp]

Item 80: A typical source of error is (transitively) including the same header file in many compilation units. This is an ODR violation. Instead, make a separate copy of that header file for each source file. #cplusplus #cpp #affectivecpp

[Affective C++ @AffectiveCpp]

@pradeepg73 @jfbastien Yes, this is a joke account.

[Affective C++ @AffectiveCpp]

Item 79: Choosing the right data structure is critical. Is memset too slow? Consider memunordered_set instead, to avoid the red-black tree in favor of hashing. See also memmap for key/value, mempriority_queue, memstack, etc. (thanks @jfbastien) #cplusplus #cpp #affectivecpp

[Affective C++ @AffectiveCpp]

@ivan_cukic Thanks to @frontier723 for the tip!

[Affective C++ @AffectiveCpp]

Item 78: With multiply wrapped objects, such as unique_ptr to optional, if you want to access a member of wrapped object, use the long arrow operator. Instead of v.get()->value().member, do v--->member. @ivan_cukic explains: https://t.co/a966EUktii #cplusplus #cpp #affectivecpp

[Tony Van Eerd @tvaneerd]

@david_m_stone But `unsigned const int` is not the same as `const unsigned int` nor `unsigned int const`.

For east-const builds unsigned const int makes the high bit read-only.
For west-const builds it makes everything *except* the high bit read-only.

We rejected central due to the ambiguity.

[Affective C++ @AffectiveCpp]

Item 77: The difference between char and wchar_t is that char is for narrow characters, and wchar_t is for wide characters. Store letters like i and j in a char, and letters like m and w in a wchar_t. (Thanks @chrisoldwood) #cplusplus #cpp #affectivecpp

[Chris Oldwood @chrisoldwood]

The difference between char and wchar_t in C++ is that char is for narrow characters and wchar_t is for wide characters. So you’d store letters like i, l, and t in a char but M and W in a wchar_t…

[Affective C++ @AffectiveCpp]

@sbjoshi @luceraproject Yeah when it comes to implicit conversions, C++ unfortunately got the defaults wrong. (Let's blame C.)

[Affective C++ @AffectiveCpp]

Really cool article about C++23! https://t.co/EWiXUeSmAu

[Affective C++ @AffectiveCpp]

@sbjoshi It's not my article, but I wish it was! :)

[Affective C++ @AffectiveCpp]

@sbjoshi Check the publishing date of the article.

[Jonathan O'Connor @ninkibah]

@ciura_victor Pro-tip: Commas are quicker to parse than semi-colons because there are less pixels in the character. @AffectiveCpp

[Jonathan O'Connor @ninkibah]

@AffectiveCpp this is how the professionals structure projects.

[Lynn (finally free) @chordbug]

programming protip! when you see x >= 0, that's a handy shortcut for

x = x > 0