Great examples, great explanations, and very thought provoking. As you work through the book, you will ponder several items in the examples.
Then, the next paragraph will begin with 'You're thinking that that won't work, but ...'. If you want to learn better, safer C++, this book may be for you.
This book covers the unwritten rules that will help you write and use better coding practices, without changing everything about the way you think and work. Meyers gives advise about safer pointer casting, better memory management, finding bugs before they find you, and the differences between lab-condition coding and real-world coding.
If you have ever had a customer call back with a bug, then the ideas presented in this book may help you think about how to change that. He also covers the most elegant and efficient ways to hide your data, your implementation, or any combination thereof.
Ever wonder why multiple inheritance doesn't work as well as you though it would, but you know you want to re-use modules of code in your hierarchy? Meyers explains away the mystery between the "is-a", "has-a", and "is-implemented-in-terms-of" connections between code. And, to top it off, he does this in an entertaining, engaging way.
This book has been moved to the front of the reference stack, and should be used intensely during the code module design phase, as well as during implmentation.