I’m happy to announce that after few months of work, the C++ Lambda Story book got translation into Spanish! Have a look at the background story and learn more about Lambdas :) This post is possible with the effort of Javier Estrada. Javier is a software developer living in sunny Southern California, and while he has flirted with Java and Python in the past, his true love is C++.

In April, we got a new book - from two Polish authors - Piotr and Adrian - on C++ Software Architecture. This one is fascinating and refreshing. While it won’t teach you all the latest C++ features or low-level tricks in our favorite language, it will move you to a higher level with architecture, building, patterns, design, and development for the cloud.

The work on C++23 continues! Without the face-to-face meetings, the Committee gathers online and discusses proposals and new additions to the language. See my latest report on what changed in C++ in April, May, and June 2021. Let’s start! Disclaimer: the view presented here is mine and does not represent the opinion of the ISO C++ Committee.

More than a year ago I started my Patreon page! It was an experiment, and I’m pleased that it has a lot of benefits. In this short blog post, I’d like to make a small summary, share my thoughts and plans for the next year. You can also learn how to get “one year” of my extra C++ content!

std::visit from C++17 is a powerful utility that allows you to call a function over a currently active type in std::variant. In this post, I’ll show you how to leverage all capabilities of this handy function: the basics, applying on multiple variants, and passing additional parameters to the matching function.

Back in 2016, an intriguing article appeared on Reddit: “Do Experienced Programmers Use Google Frequently?”. The author discussed if expert programmers use google more often than novice coders. He mentioned that using google is a good thing. It helps to find the best solutions, validate ideas, speed the development. Google nowadays seems to be a crucial part of any developer toolbox.

This blog post will show you how to create a robust and scalable logging library using lots of Modern C++ techniques. The author successfully used this code on Arduino embedded environment and various other production areas. Let’s dive right in. Written by Stephen Dolley Stephen works with C++ commercial and government development teams to upgrade their skills and improve the expressiveness and robustness of their code.

With C++17 we get another facility to handle the conversion between text and numbers. Why should we care about the new routines? Are they better in any way? Before C++17   C++, before C++17, offered several options when it comes to string conversion: sprintf / snprintf sscanf atol strtol strstream stringstream to_string stoi and similar functions And with C++17 you get another option: std::from_chars!

In this post, I’ll show you how to use the newest, low-level, conversion routines form C++17. With the new functionality, you can quickly transform numbers into text and have super performance compared to previous techniques. Before C++17   Until C++17, we had several ways of converting numbers into strings: sprintf / snprintf stringstream to_string itoa and 3rd-party libraries like boost - lexical cast And with C++17 we get another option: std::to_chars (along with the corresponding method from_chars) !

The problem: a library function offers several overloads, but depending on the implementation/compiler, some of the overloads are not available. How to check the existence of an overload? And how to provide a safe fallback? In this article, I’ll show you a background “theory” and one case - std::from_chars that exposes full support for numbers or only integer support (in GCC, Clang).

Do you know how many ways we can implement a filter function in C++? While the problem is relatively easy to understand - take a container, copy elements that match a predicate and the return a new container - it’s good to exercise with the Standard Library and check a few ideas.

A single-precision floating-point number is represented by 32 bits and hides various wonderful encoding techniques. However, some of those tricks might cause some imprecise calculations so it’s crucial to know how to work with those numbers. Let’s have a look at three common misconceptions. This is a guest post from Adam Sawicki