Nicolai M. Josuttis
Autor von The C++ Standard Library: A Tutorial and Reference
Über den Autor
Nicolai M. Josuttis is an independent technical consultant who designs object-oriented software for the telecommunication, traffic, finance, and manufacturing industries. He is an active member of the C++ Standard Committee library working group and a partner at System Bauhaus, a German group of mehr anzeigen recognized object-oriented system development experts. Josuttis has written several books on object-oriented programming and C++, including Die C++-Standardbibliothek and Objektorientiertes Programmieren in C++. weniger anzeigen
Werke von Nicolai M. Josuttis
Getagged
Wissenswertes
- Geburtstag
- 1950s
- Geschlecht
- male
- Nationalität
- Deutschland
Mitglieder
Rezensionen
Listen
Dir gefällt vielleicht auch
Statistikseite
- Werke
- 10
- Mitglieder
- 580
- Beliebtheit
- #43,223
- Bewertung
- 4.3
- Rezensionen
- 5
- ISBNs
- 22
- Sprachen
- 2
- Favoriten
- 1
In other words, the book -- or at least my copy -- is incomplete. Nothing warned me before I bought it that that was the case. Indeed, the author's web page stated that the hardcopy book was "100%" complete.
In the text, the English is only rarely ambiguous or confusing, although it is more frequently rendered in a manner that a native speaker of the language (or at least this native speaker of the language) finds stilted and slightly unnatural.
While the book seems solid on the mechanics of the new C++20 features, and contains many pieces of example code illustrating their use, nowhere does it provide something that would be at least as useful: explanations of why they were added to the language, and when to use them.
C++20 is somewhat of a monster, and I have yet to see clear explanations of why, for example, one might choose to use ranges or coroutines to solve a problem over other, more conventional, methods. For the most part, the new features don't seem to involve writing *less* code, just *different* code. And while I can imagine that, for example, range-based code might result in more efficient executable code at the CPU level, I have seen, neither in this book nor elsewhere, any objective measurements to suggest that reformulating the manner in which loops over containers are written so as to use ranges actually results in programs that are more efficient.
Similarly, coroutines are a complex new feature that we have managed without until now; so why are they suddenly a good thing? All the examples of their use that I have seen are basically an inordinately complicated way to solve a not-very-practical problem that I have never seen occur in real life.
So, while this book is very good as a reference for the new features, there is definitely room for a more descriptive book to explain why and when to use the features that this book (mostly) describes so well.… (mehr)