Effective C++: 55 Specific Ways to Improve Your Programs and Designs

Outdated, (you won't have a private inheritance of uncopyable class anymore, etc).This is among the books that we all begin from though.

Leggevo online diverse recensioni che indicavano il libro come obsoleto. L'ho trovato invece pieno di spunti interessanti, e negli ultimi capitoli c'è un introduzione ottima al razionale che c'è dietro al meta programming con i template.Ovviamente non sono un esperto di C++ quindi è possibile che uno sviluppatore senior possa trovarlo datato, ma se state imparando da poco il linguaggio, questo libro vi sarà utilissimo.

So... I read alot 1 or 2 star reviews for this book and many mention that Meyers either doesn't go into enough detail or he explains things that are rather obvious to most C++ programmers.I'll tell you a bit of my background and why this book is a goldmine for someone like me:I have a degree in electrical engineering. I did some C++ programming in college but never got to the OOP stuff when I was in school. As I changed jobs over the years eventually I landed in a position where I needed to manage an existing C++ system. I learned the basics of OOP just by doing some reading online and picked it up over the years as most engineers are able to do. I got to the point where I was very familiar with the system and for the most part I could do pretty much everything I needed do for my job.But my only formal training on C++ barely even scratched the surface of its capabilities, so I thought I should read a book on some "good practices" in C++.This book was exactly what I was looking for. Coming in at under 300 pages, and with Meyers listing 55 specific items, this only leaves approximately 5 pages per item. This of course means that this book is not the definitive C++ reference guide. That said, this is not a book for beginners. I would say that you should be practicing OOP within C++ for at least a year before reading this book. (But it probably also isn't a book for experts either, because experts probably already know mostly everything in this book.)Many of the items in this book are structured like this:1) Meyers shows some snippet of code that looks innocent at first glance.2) He explains how this could result in disaster if the exact wrong series of events happen (and provides a basic example of how this might unfold).3) Then he explains how to modify the code to avoid this behavior. (Although, there are some dark corners of C++ that unfortunately can't be completely prevented from happening, even with proper class design. For these, Meyers explains how to minimize these chances of happening.)This structure is very easy to understand and effective for retaining the information in this book.In conclusion, I would recommend this book to anyone who understands the rules/syntax of C++ and has been using it for a few years, but maybe needs some guidance in taming the C++ beast.

Fantastic book, filled with many pointers (I'm sorry) on writing efficient and maintainable code. It's also small which makes it handy for carrying around and it's straight to the point which makes it awesome for when you're doing a project, you just go to the index and find what you want, read it and you have an exact understanding of what's going on and how to implement it in your own projects.

Reçu en parfait en état.Très bon livre, je recommande fortement à tout développeur souhaitant se perfectionner en orienté objet.Se lit très facilement.