"Two of the world's most respected C++ experts distill the experience of the global C++ community into a set of coding standards that every developer and development team can understand and use as a basis for their own coding standards." The authors cover virtually every facet of C++ design and coding style, functions, operators, class design, inheritance, construction/destruction, copying, assignment, namespaces, modules, templates, genericity, exceptions, STL containers and algorithms, and more. Each standard is described concisely, with practical examples. From type definition to error handling, this book presents C++ best practices, including some that have only recently been identified and standardized-techniques you may not know even if you've used C++ for years.
From 2004 - in some senses, almost all the advice is still fairly relevant. That said, I wonder how many of a 101 rules set today would map to this original one. Does remind you though of the gory details of the language, and it is fairly pithy, with most items just being one or two pages with some examples and exceptions and references.
This was a 3-star book based on writing style that got a boost to 4 due to the quality and usefulness of the information it contained.
The information was presented in semi-list form with only a page or two to explain each point. I found that format to be lacking in the details and especially the examples that I would have liked and that would have made it much more clear and easier to understand. The book was probably intended for programmers with more skill and knowledge than I have, which I think contributed to my finding a lot of the information to be difficult to comprehend.
The tips were very useful though, and I suspect I'll be referring back to this in the future both to refresh my memory and to grasp the information better as I become more experienced.
A useful and interesting collection of guidelines for writing C++. Some of the guidelines are "obvious," but his other reviews have noted, worth repeating. Others are not so obvious and demonstrate subtle traps. One big flaw is that, particularly for the subtle cases, they don't go into enough detail -- they explain that something is bad, maybe even give an example, but not enough to really understand The intricacies of why.
I felt that Scott Meyers' books did a much better job of explaining the why, and where they overlap, you should read his first. Unfortunately, Meyers doesn't cover everything.
Sometimes it's good to repeat the obvious... Don't optimize prematurely, don't write list.size() == 0 when list.isEmpty() would have accomplished the same, ... Apart from that, this book also covers 99 other recurring pitfalls and misuses in C++ programming. Most of them also apply to other programming languages.
This book is "a must" for people involved in software development. The book discusses good programming practices. Though a reader should have enough experience to appreciate advises of this book.
A very good book, full of practical advice for the serious programmer. However there's one big problem with this book; all the information you need can be found in the table of contents!