Effective C++ Third Edition

By:

Meyers, Scott

Material type: Text

TextPublication details: New York: Addison-Wesley: 2008Edition: 3EISBN:

9780321334879

Other title:

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

Subject(s):

C++ Software Development

DDC classification:

005.133 Mey

Holdings
Item type	Current library	Call number	Copy number	Status	Date due	Barcode
Standard Loan	Thurles Library Main Collection	005.133 MEY (Browse shelf(Opens below))		Available		R17165YKRC
Standard Loan	Thurles Library Main Collection	005.133 MEY (Browse shelf(Opens below))	1	Available		R17166AKRC

Enhanced descriptions from Syndetics:

"Every C++ professional needs a copy of Effective C++. It is an absolute must-read for anyone thinking of doing serious C++ development. If you've never read Effective C++ and you think you know everything about C++, think again."
-- Steve Schirripa, Software Engineer, Google "C++ and the C++ community have grown up in the last fifteen years, and the third edition of Effective C++ reflects this. The clear and precise style of the book is evidence of Scott's deep insight and distinctive ability to impart knowledge."
-- Gerhard Kreuzer, Research and Development Engineer, Siemens AG

The first two editions of Effective C++ were embraced by hundreds of thousands of programmers worldwide. The reason is clear: Scott Meyers' practical approach to C++ describes the rules of thumb used by the experts -- the things they almost always do or almost always avoid doing -- to produce clear, correct, efficient code.

The book is organized around 55 specific guidelines, each of which describes a way to write better C++. Each is backed by concrete examples. For this third edition, more than half the content is new, including added chapters on managing resources and using templates. Topics from the second edition have been extensively revised to reflect modern design considerations, including exceptions, design patterns, and multithreading.

Important features of Effective C++ include:

Expert guidance on the design of effective classes, functions, templates, and inheritance hierarchies. Applications of new "TR1" standard library functionality, along with comparisons to existing standard library components. Insights into differences between C++ and other languages (e.g., Java, C#, C) that help developers from those languages assimilate "the C++ way" of doing things.

Table of contents provided by Syndetics

Preface (p. xv)
Acknowledgments (p. xvii)
Introduction (p. 1)
Chapter 1 Accustoming Yourself to C++ (p. 11Item)
1 View C++ as a federation of languages (p. 11 Item)
2 Prefer consts, enums, and inlines to #defines (p. 13 Item)
3 Use const whenever possible (p. 17 Item)
4 Make sure that objects are initialized before theyre used (p. 26)
Chapter 2 Constructors, Destructors, and Assignment Operators (p. 34Item)
5 Know what functions C++ silently writes and calls (p. 34 Item)
6 Explicitly disallow the use of compiler-generated functions you do not want (p. 37 Item)
7 Declare destructors virtual in polymorphic base classes (p. 40 Item)
8 Prevent exceptions from leaving destructors (p. 44 Item)
9 Never call virtual functions during construction or destruction (p. 48 Item)
10 Have assignment operators return a reference to *this (p. 52 Item)
11 Handle assignment to self in operator= (p. 53 Item)
12 Copy all parts of an object (p. 57)
Chapter 3 Resource Management (p. 61Item)
13 Use objects to manage resources (p. 61 Item)
14 Think carefully about copying behavior in resource-managing classes (p. 66 Item)
15 Provide access to raw resources in resource-managing classes (p. 69 Item)
16 Use the same form in corresponding uses of new and delete (p. 73 Item)
17 Store newed objects in smart pointers in standalone statements (p. 75)
Chapter 4 Designs and Declarations (p. 78Item)
18 Make interfaces easy to use correctly and hard to use incorrectly (p. 78 Item)
19 Treat class design as type design (p. 84 Item)
20 Prefer pass-by-reference-to-const to pass-by-value (p. 86 Item)
21 Dont try to return a reference when you must return an object (p. 90 Item)
22 Declare data members private (p. 94 Item)
23 Prefer non-member non-friend functions to member functions (p. 98 Item)
24 Declare non-member functions when type conversions should apply to all parameters (p. 102 Item)
25 Consider support for a non-throwing swap (p. 106)
Chapter 5 Implementations (p. 113Item)
26 Postpone variable definitions as long as possible (p. 113 Item)
27 Minimize casting (p. 116 Item)
28 Avoid returning handles to object internals (p. 123 Item)
29 Strive for exception-safe code (p. 127 Item)
30 Understand the ins and outs of inlining (p. 134 Item)
31 Minimize compilation dependencies between files (p. 140)
Chapter 6 Inheritance and Object-Oriented Design 149Item
32 Make sure public inheritance models is-a (p. 150 Item)
33 Avoid hiding inherited names (p. 156 Item)
34 Differentiate between inheritance of interface and inheritance of implementation (p. 161 Item)
35 Consider alternatives to virtual functions (p. 169 Item)
36 Never redefine an inherited non-virtual function (p. 178 Item)
37 Never redefine a functions inherited default parameter value (p. 180 Item)
38 Model has-a or is-implemented-in-terms-of through composition (p. 184 Item)
39 Use private inheritance judiciously (p. 187 Item)
40 Use multiple inheritance judiciously (p. 192)
Chapter 7 Templates and Generic Programming 199Item
41 Understand implicit interfaces and compile-time polymorphism (p. 199 Item)
42 Understand the two meanings of typename (p. 203 Item)
43 Know how to access names in templatized base classes (p. 207 Item)
44 Factor parameter-independent code out of templates (p. 212 Item)
45 Use member function templates to accept all compatible types (p. 218 Item)
46 Define non-member functions inside templates when type conversions are desired (p. 222 Item)
47 Use traits classes for information about types (p. 226 Item)
48 Be aware of template metaprogramming (p. 233)
Chapter 8 Customizing new and delete 239Item
49 Understand the behavior of the new-handler (p. 240 Item)
50 Understand when it makes sense to replace new and delete (p. 247 Item)
51 Adhere to convention when writing new and delete (p. 252 Item)
52 Write placement delete if you write placement new (p. 256)
Chapter 9 Misc

Excerpt provided by Syndetics

I wrote the original edition of Effective C++ in 1991. When the time came for a second edition in 1997, I updated the material in important ways, but, because I didn't want to confuse readers familiar with the first edition, I did my best to retain the existing structure: 48 of the original 50 Item titles remained essentially unchanged. If the book were a house, the second edition was the equivalent of freshening things up by replacing carpets, paint, and light fixtures. For the third edition, I tore the place down to the studs. (There were times I wished I'd gone all the way to the foundation.) The world of C++ has undergone enormous change since 1991, and the goal of this book -- to identify the most important C++ programming guidelines in a small, readable package -- was no longer served by the Items I'd established nearly 15 years earlier. In 1991, it was reasonable to assume that C++ programmers came from a C background. Now, programmers moving to C++ are just as likely to come from Java or C#. In 1991, inheritance and object-oriented programming were new to most programmers. Now they're well-established concepts, and exceptions, templates, and generic programming are the areas where people need more guidance. In 1991, nobody had heard of design patterns. Now it's hard to discuss software systems without referring to them. In 1991, work had just begun on a formal standard for C++. Now that standard is eight years old, and work has begun on the next version. To address these changes, I wiped the slate as clean as I could and asked myself, "What are the most important pieces of advice for practicing C++ programmers in 2005?" The result is the set of Items in this new edition. The book has new chapters on resource management and on programming with templates. In fact, template concerns are woven throughout the text, because they affect almost everything in C++. The book also includes new material on programming in the presence of exceptions, on applying design patterns, and on using the new TR1 library facilities. (TR1 is described in Item54.) It acknowledges that techniques and approaches that work well in single-threaded systems may not be appropriate in multithreaded systems. Well over half the material in the book is new. However, most of the fundamental information in the second edition continues to be important, so I found a way to retain it in one form or another. (You'll find a mapping between the second and third edition Items in Appendix B.) I've worked hard to make this book as good as I can, but I have no illusions that it's perfect. If you feel that some of the Items in this book are inappropriate as general advice; that there is a better way to accomplish a task examined in the book; or that one or more of the technical discussions is unclear, incomplete, or misleading, please tell me. If you find an error of any kind -- technical, grammatical, typographical, whatever -- please tell me that, too. I'll gladly add to the acknowledgments in later printings the name of the first person to bring each problem to my attention. Even with the number of Items expanded to 55, the set of guidelines in this book is far from exhaustive. But coming up with good rules -- ones that apply to almost all applications almost all the time -- is harder than it might seem. If you have suggestions for additional guidelines, I would be delighted to hear about them. I maintain a list of changes to this book since its first printing, including bug fixes, clarifications, and technical updates. The list is available at the Effective C++ Errata web page, http://aristeia.com/BookErrata/ec++3e-errata.html . If you'd like to be notified when I update the list, I encourage you to join my mailing list. I use it to make announcements likely to interest people who follow my professional work. For details, consult http://aristeia.com/MailingList/ . Scott Douglas Meyers Stafford, Oregon April 2005 http://aristeia.com/ Excerpted from Effective C++: 55 Specific Ways to Improve Your Programs and Designs by Scott Meyers All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.

Author notes provided by Syndetics

Scott Meyers is one of the world's foremost authorities on C++, providing training and consulting services to clients worldwide. He is the author of the best-selling Effective C++ series of books (Effective C++, More Effective C++, and Effective STL) and of the innovative Effective C++ CD. He is consulting editor for Addison Wesley's Effective Software Development Series and is a founding member of the Advisory Board for The C++ Source ( http://www.artima.com/cppsource ). He holds a Ph.D. in Computer Science from Brown University. His web site is http://www.aristeia.com .