More Effective C++: 35 New Ways to Improve Your Programs and Designs

Effective C++ #2

by Scott Meyers

More than 150,000 copies in print! Praise for Scott Meyers’ first book, Effective C++ : “I heartily recommend Effective C++ to anyone who aspires to mastery of C++ at the intermediate level or above.”
– The C/C++ User’s Journal From the author of the indispensable Effective C++ , here are 35 new ways to improve your programs and designs. Drawing on years of experience, Meyers explains how to write software that is more effective : more efficient, more robust, more consistent, more portable, and more reusable. In short, how to write C++ software that’s just plain better. More Effective C++ More Effective C++ is filled with pragmatic, down-to-earth advice you’ll use every day. Like Effective C++ before it, More Effective C++ is essential reading for anyone working with C++.

Genres: Programming, Computer Science, Technical, Nonfiction, Software, Computers, Technology

318 pages, Paperback

First published January 8, 1995

About the author

Scott Douglas Meyers is an American author and software consultant, specializing in the C++ computer programming language. He is known for his Effective C++ book series. During his career, he was a frequent speaker at conferences and trade shows.

Reviews

[Rick Muële · Rating 5 out of 5]

If you are a programmer, you must read it! It is full of good exapmles of how to write better code and design things right.

[Elliott Bignell · Rating 4 out of 5]

I have owned this book for several years and typically re-read it about every year or so. To say that a book is necessary reading is sometimes hyperbolic, but if you want to understand C++ then it is probably the truth in this case, if less so than for Meyers' first book. Meyers has written three books on C++ - "Effective C++", this volume, and "Effective STL". You, fellow programmer, need them all. Plus "Design Patterns", of course. Stroustrup and the ACR probably belong beside them, but Meyers is uniquely readable. He's even funny. Some C++ experts will point to Stroustrup as the basis of your library. I have a copy of that, but I would not describe it as learning material; it is reference material. You can actually read Meyers for pleasure and for learning, and that's an unusual combination to find in software literature.

Meyers will help you get the best out of C++. If you can write classes in Java, C# or, heaven forfend, Visual Basic, then you can certainly write them in C++ and come up with a working design. That is not the same as using the language effectively. C++ is a work of beauty, but it has many pitfalls and it requires some depth of knowledge to get the best out of it. It's also portable, and Meyers knows how to write portable code, which must surely be a consideration with Ubuntu Linux and Apple advancing into the market. All genuine C++ compilers comply with an ISO/ANSI standard, which in theory means that properly-designed C++ code will compile on any conformant compiler and can be ported to any chipset for which a compiler exists. In practice, of course, this is not quite so easy. Meyers is very familiar with the standard and has been involved in its evolution, which along with his experience of developing in C++ positions him perfectly to point out where portability can and cannot be taken for granted.

The book is divided into 35 items, any of which will do you nicely for the train-journey to work. It is divided into "Basics", "Operators", "Exceptions", "Efficiency", "Techniques" and "Miscellany". It also throws in an auto_ptr implementation, which I would advise any C++ developer to study in detail, as smart pointers are one of the jewels of C++ design. (I would also then advise you to use the shared_ptr supplied with boost, as you will not find a better implementation.) Smart pointers are, in fact, a perfect synecdoche of the broader epiphany that you will go through as you master C++, and illustrate why Meyers is so worth reading. They can take the place of the garbage-collector in the more highly-managed languages, as they provide a way to guarantee that clean-up (or other) code is performed when a code section is exited - no matter how it is exited, if you also follow Meyers' advice on exception-handling. What this means is no more "delete" in your life. You hand the resource over to your smart pointer and the smart pointer cleans it up when its lifetime is over, no matter how many times "return" appears in a function, and even if the code section exits due to an exception. The standard also provides guarantees that this happens in a particular sequence and at a particular time during stack unwinding, in contrast to the vagaries and runtime cost of commercial garbage-collectors. I won't micturate on Meyers' geraniums by describing the mechanism in detail, but this should demonstrate the worth of mastering the C++ idiom.

See-also list:
Effective C++: 55 Specific Ways to Improve Your Programs and Designs (3rd Edition)
Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library
Design Patterns: Elements of Reusable Object-Oriented Software

[Ken · Rating 3 out of 5]

Skip this book. There's some interesting and useful content relating to exceptions and casting, in case you haven't encountered that advice elsewhere, but otherwise the material is largely dated. In addition, some of the recommendations in the Techniques section are IMO too clever by half, and not really good advice for maintainable software. Meyers is a great author with a great understanding of C++, but this book should be left behind in favor of other ones.

[Kuba · Rating 2 out of 5]

If you're beginner - skip it or if you really want you can read carefully about basics, operators and exceptions. Especially don't read Techniques chapter as you could learn pure evil techniques like trying to find out if object is on heap which I wish I never read.

If you're advanced - skip it as well. You're not gonna learn anything new and it will spare you irritation and screaming "PLEASE, DON'T DO THAT" while reading Techniques chapter.

I think this book could be great 20 years ago, but right now too many things are outdated and I mean really outdated. Huge dissapointment after amazing Effective C++.

[Filippo Pacifici · Rating 5 out of 5]

This is the best C++ book I read so far. (you should already know the basics of the language).
It is also incredibly scary in some parts.

[Xavrin · Rating 2 out of 5]

Many things in this book didn't seem very interesting to me. Some of them I knew before, some have doubtful use in a modern programming.
Some of the presented techniques were trying to solve problems that you should almost never try to solve: e. g. find out if your object is constructed on the heap or force that there are at most N objects of your class.

[Benoit Blanchon · Rating 3 out of 5]

Unfortunately, this one is not as good as the others Effective C++.
It's less practical and too wordy.

[James · Rating 4 out of 5]

Still awesome, but get the newer version!

[Christopher Olekas · Rating 4 out of 5]

Needs to be updated with C++14/17 usage

[Shyam Poovaiah]

After reading effective cpp this is a great book to read. Really points out subtleties in C++ and a lot of pointers to write great code.

[Laurynas Biveinis · Rating 3 out of 5]

Three star rating does not capture it. In 2022 there are better choices to learn the modern C++, however this was definitely a five-star book in the time of C++98.

[Alan Ramsay · Rating 5 out of 5]

More of the same easily digestible insights into opportunities and risks hidden in the intricacies of C++

[LustHeroin · Rating 5 out of 5]

Based. Try to solve this, C++ nerd

[Mickey Kawick · Rating 4 out of 5]

Gave me a great background years ago and deals a bit with design patterns.

[Prakash · Rating 4 out of 5]

I get why Scott Meyers is such a celebrated author in the C++ world.

This is a sequel to the Effective C++ but is older because it was last edited in 1996-97.

There is a lot of wisdom and effective design issues discussed in the book. There is also the miscellany section which will help you become a better C++ programmer if not immediately providing you something practical.

Meyer's quite funny in this book and the itemized style works great as it did in Effective C++. (And it will in Effective Java & JCIP in future)

Not bad for a 20 year old book. I only take off a star as it is bit too wordy at some places.

[Alex · Rating 5 out of 5]

This particular book is rather old among the other books in the series but very helpful nonetheless. All books by Scott Meyers are just must-read for any C++ dev (arguably even more so than the books by the language author himself). What I like about the book (and the whole series) is that they do not meticulously list all the language features where the API reference can suffice. Rather, they provide a practical advice on how to use C++ effectively (and efficiently) while avoiding the numerous traps which sadly C++ excels at setting.

[Kirill · Rating 5 out of 5]

Never aging classic, although some items from 1995 are deprecated - like auto_ptr. Most of all liked the "Techniques"- Items. It was a pleasure to read about reference counting, double dispatch and prohibiting heap-based objects.

Fond of the Scott's sparkling sense of humor, just like here:
"Programmers looking for a C++ compiler can ask vendors whether the return value optimization is implemented. If one vendor says yes and another says "The what?", the first vendor has a notable competitive advantage. Ah, capitalism. Sometimes you just gotta love it."

[Flavio Perri · Rating 4 out of 5]

It was really great: I learn a lot of things about C++ designs and language traps. I give it 4/5 because it's a little dated (edited in 1997): few things were already explained in Effective C++ Third Edition (edited recently), and compilers now support most of the "future" features mentioned.
Beside this, the book it's really good, I hope it will come out with a new edition.
I'll start soon the third book of Meyers (Effective STL)

[Alexander]

I found most of the book to be a little too wordy and some of the examples are not as concise as they could've been. But some tips were useful. The author talks mostly about general concepts that apply to c++ without too much referencing to STL. It's a very good book for people without too much experience with c++.

[mekin · Rating 5 out of 5]

Must read & must have for all c++ developers

[Patrick · Rating 4 out of 5]

Great way to get up to speed with post-1998 C++

[gargamelscat · Rating 4 out of 5]

Just great - still after all these years. A must read for any C++ developer.

[Timothy Culp · Rating 5 out of 5]

The inspiration behind most designs in the Origin baseline. Skip Effective C++ and jump right to this gem.

[Manjunatha Krishnamurthy]

book that every software engineer who is working in C/C++ must read

[Craig · Rating 4 out of 5]

Good read, A bit out-dated and most of it has now been covered in Effective C++ (Third Edition) so should just read that instead :)

[Rembo666 · Rating 5 out of 5]

A worthy addition to the original.

[Arvydas Sidorenko · Rating 5 out of 5]

Invaluable resource. There shouldn't exist a single C++ programmer who haven't read this!

[Benjamin · Rating 4 out of 5]

Very insightful, but a little dated, hence only 4/5 stars.

[Artem Komisarenko · Rating 5 out of 5]

Must read для плюсовика.

[Jia Chen · Rating 5 out of 5]

One of the must-read books for learning C++