The Synchronizes-With Relation -- Jeff Preshing
Here is a nicely accessible description of synchronization in the C++ memory model:
The Synchronizes-With Relation
by Jeff Preshing
See also Jeff's other recent related posts:
Articles & Books
C++: Polymorphic Cloning and the CRTP (Curiously Recurring Template Pattern)--Katy Coe
On CRTP with multi-level inheritance, cloning, and the constructor forwarding problem.
C++: Polymorphic cloning and the CRTP (Curiously Recurring Template Pattern)
by Katy Coe
From the article:
A common problem in C++ occurs when you have an object of an unknown derived type and want to make a copy of it. ...
The solution is to use the commonly-used polymorphic cloning pattern. In this pattern, we define a virtual function -- which we’ll call
clone()in this article -- which when called via an object pointer returns a new object of the correct derived type.
Moving Data and Address Arithmetic -- Andrew Koenig
Today on Dr. Dobb's:
Moving Data and Address Arithmetic
by Andrew Koenig
From the article:
Programs that don't care about the addresses of their data rarely need to move those data. After all, we can view the whole point of moving an object as a way of changing the object's address without changing its contents...
noexcept Destructors -- Andrzej Krzemieński
A slight change from C++98 to C++11, tightening up destructor semantics. Yes, it's still considered a best practice to never allow an exception to escape from a destructor -- in any language with destructor or Dispose functionality -- and now we have an additional reason in C++11:
noexcept Destructors
by Andrzej Krzemieński
From the article:
The goal of this post is to show one — fairly small — backwards incompatibility in C++11. It shows how
noexceptexception specifications are implicitly generated for your destructors. In short, the following program used to run successfully in C++03 (under some definition of “success”): ...In this post I do not intend to argue whether it is a bad practice or not to throw from destructors, but focus on what happens when you do. But I really do not encourage you to throw from destructors...
GotW #7a Solution: Minimizing Compile-Time Dependencies, Part 1—Herb Sutter
The solution to the latest GotW problem is now available. In this Item, the focus is on analyzing and managing compile-time dependencies.
GotW #7a Solution: Minimizing Compile-Time Dependencies, Part 1
by Herb Sutter
From the article:
Managing dependencies well is an essential part of writing solid code. C++ supports two powerful methods of abstraction: object-oriented programming and generic programming. Both of these are fundamentally tools to help manage dependencies, and therefore manage complexity. It’s telling that all of the common OO/generic buzzwords—including encapsulation, polymorphism, and type independence—along with most design patterns, are really about describing ways to manage complexity within a software system by managing the code’s interdependencies.
When we talk about dependencies, we usually think of run-time dependencies like class interactions. In this Item, we will focus instead on how to analyze and manage compile-time dependencies. As a first step, try to identify (and root out) unnecessary headers.
Guideline: Never #include unnecessary header files.
Guideline: Prefer to #include <iosfwd> when a forward declaration of a stream will suffice.
Guideline: Never #include a header when a forward declaration will suffice.
Resumable Functions: async and await -- Jens Weller
A look at resumable functions:
Resumable Functions: async and await
by Jens Weller
From the article:
While I did my series about the papers for Bristol, there was one paper, which I personally found a bit weird. This paper was about resumable functions, and at that time it was just another paper full of ideas for C++ to me. At C++Now suddenly, I got a better insight to what the use of resumable functions could be...
Functional C++: Type Classes -- whanhee
A nice series on functional programming in C++
Functional C++: Type Classes
by whanhee
From the article
Type classes are a feature of Haskell which is very similar to the upcoming Concepts. Both define interfaces to a data type, which can be defined separately from the data, in contrast to member functions...
C++ String to Int -- Ivan Neeson
A nice comparison on converting a string to int:
C++ String to Int
by Ivan Neeson
From the article:
In this post I will compare the following methods for parsing a string into an integer in C++:
- Manually
atoi()strtol()sscanf()std::stoi(C++11 only)std::istringstream- Boost.LexicalCast
- Boost.LexicalCast with C locale
- Boost.Spirit.Qi
- Boost.Coerce
Overload 116 available
Overload 116 is now available. It contains the following articles, and more:
Overload 116
Auto -- A Necessary Evil? Part 2 -- Roger Orr
When is the use of auto good, and when is it evil?
Dynamic C++, Part 2 -- Alex Fabijanic
Alex Fabijanic and Richard Saunders continue to explore dynamic solutions in C++.
Portable String Literals in C++ -- Alf Steinbach
How hard can it be to make a file in C++ with international text literals in its name? Alf Steinbach shows us how to write a file called π.recipe.
Hard Upper Limit on Memory Latency -- Sergey Ignatchenko
How low can latency really get?
... and more!
Quick Q: What does override do? -- StackOverflow
Recently on SO:
override keyword in C++
I am a beginner in C++. I have come across
overridekeyword used in the header file that I am working on. May I know, what is real use ofoverride, perhaps with an example would be easy to understand.