Let's recapitulate. I have written about 100 posts on the C++ Core Guidelines in the last two years. Why? The document answers:  "This document is a set of guidelines for using C++ well. this document aims to help people to use modern C++ effectively.". But my story does not end here. The guidelines have a supporting section.

Before I write about the very popular RAII idiom in C++, I want to present you with a trick, which is often quite handy, when you repeatedly search for a text pattern:  use negative search.

There is more to write about the usage of regular expressions than I wrote in my last post The Regular Expression Library. Let's continue.

My original plan was to write about the rules of the C++ Core Guidelines for the regex and chrono library, but besides the subsection title, no content is available. I already wrote a few posts about time functionality. So I'm done. Today, I fill the gap and write about the regex library.

As easy as my title and the rules of the C++ core guidelines sound, getting more performance out of the iostreams is no no-brainer.

Today's post is about what you should know about Iostreams. In particular, I write about formatted and unformatted In- and Output.

When you interact with the outside world, the iostream library is the way to go in C++. As always, you have to keep a few rules in mind. Let me show which rules.

The C++ core guidelines use the term string as a sequence of characters. Consequently, the guidelines are about  C-strings, C++-strings, the C++17 std::string_view's, and std::byte's. 

When you access an element outside a container of the STL, the result is not so promising. Your effect may be an error or undefined behavior. Undefined behavior means all bets are open.

Modern C++ has eight associative containers, but your special friends should be std::map and std::unordered_map. Why? Let me explain it in this post.