Effective C++ 3rd Edition：提升C++程序设计与优化的55个具体方法

需积分: 0 160 浏览量更新于2024-07-31 收藏 2.75MB PDF 举报

"Effective C++ 3rd Edition 是一本由 Scott Meyers 编写的关于 C++ 高级编程的书籍，旨在帮助程序员提升代码质量和效率。这本书包含55条具体建议，每一条都提供了编写更好 C++ 代码的方法，并通过实例进行支持。第三版更新了超过一半的内容，涵盖了资源管理、模板的使用以及现代设计考量，如异常处理、设计模式和多线程。" 在 "Effective C++ 3rd Edition" 中，Scott Meyers 提出了许多关键知识点，这些知识点对于任何希望深入理解和优化 C++ 编程的开发者来说都是至关重要的。以下是其中一些核心主题的详细说明： 1. **类的设计**：书中强调了类设计的重要性，包括封装、访问控制和构造函数的使用，以确保对象的状态正确性和安全性。同时，作者讨论了如何利用构造函数初始化列表、拷贝构造函数和赋值运算符来实现深拷贝和浅拷贝。 2. **函数的使用**：书中提到了函数的重载、默认参数和模板函数，以及如何避免意外的类型转换和函数重定义。此外，还讨论了 const 的正确使用，以防止意外修改和提高代码可读性。 3. **模板的深度探索**：模板是 C++ 中强大的工具，但也可能带来复杂性。Scott Meyers 分析了模板元编程，以及如何有效地使用模板特化和偏特化。他还探讨了模板和异常安全性的关系。 4. **资源管理**：书中介绍了智能指针（如 shared_ptr, unique_ptr）的概念，作为传统指针的替代，以简化内存管理和避免内存泄漏。此外，还讨论了RAII（Resource Acquisition Is Initialization）原则，这是 C++ 中管理资源的一种常见方法。 5. **继承层次结构**：在继承方面，作者强调了多态性的重要性，包括虚函数和纯虚函数的使用，以及何时应该避免使用继承。他还讨论了钻石问题及其解决方案。 6. **异常处理**：异常处理是 C++ 中一个关键的错误处理机制。书中解释了何时应抛出和捕获异常，以及如何设计异常安全的代码。 7. **多线程编程**：随着 C++11 引入了多线程支持，作者探讨了并发编程中的挑战，如线程安全、互斥量和条件变量的使用，以及如何避免竞态条件。 8. **设计模式**：虽然不是 C++ 语言本身的一部分，但设计模式是解决常见编程问题的通用解决方案。书中可能会提到一些常见的设计模式，如工厂模式、单例模式和观察者模式，并解释如何在 C++ 中应用它们。通过深入学习和实践 "Effective C++ 3rd Edition" 中的这些知识点，程序员可以提升自己的 C++ 编程技巧，写出更健壮、更高效且易于维护的代码。无论你是初学者还是经验丰富的开发者，这本书都将为你提供宝贵的洞见和指导。

Preface

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

http://aristeia.com/ APRIL 2005

< Day Day Up >

file:///D|/work/material/C++/Effective%20C++%203rd.Edition/0321334876/pref03.html（第 2／2 页）2009-1-9 14:36:29

Acknowledgments
 
 < Day Day Up >  
 
 
Acknowledgments
Effective C++ has existed for fifteen years, and I started learning C++ about five years before I wrote the book. 
The "Effective C++ project" has thus been under development for two decades. During that time, I have 
benefited from the insights, suggestions, corrections, and, occasionally, dumbfounded stares of hundreds 
(thousands?) of people. Each has helped improve Effective C++. I am grateful to them all.
I've given up trying to keep track of where I learned what, but one general source of information has helped me 
as long as I can remember: the Usenet C++ newsgroups, especially comp.lang.c++.moderated and 
comp.std.c++. Many of the Items in this book — perhaps most — have benefited from the vetting of 
technical ideas at which the participants in these newsgroups excel.
Regarding new material in the third edition, Steve Dewhurst worked with me to come up with an initial set of 
candidate Items. In Item 11, the idea of implementing operator= via copy-and-swap came from Herb Sutter's 
writings on the topic, e.g., Item 13 of his Exceptional C++ (Addison-Wesley, 2000). RAII (see Item 13) is from 
Bjarne Stroustrup's The C++ Programming Language (Addison-Wesley, 2000). The idea behind Item 17 came 
from the "Best Practices" section of the Boost shared_ptr web page, http://boost.org/libs/smart_ptr/
shared_ptr.htm#BestPractices and was refined by Item 21 of Herb Sutter's More Exceptional C++ (Addison-
Wesley, 2002). Item 29 was strongly influenced by Herb Sutter's extensive writings on the topic, e.g., Items 8-19 
of Exceptional C++, Items 17–23 of More Exceptional C++, and Items 11–13 of Exceptional C++ Style 
(Addison-Wesley, 2005); David Abrahams helped me better understand the three exception safety guarantees. 
The NVI idiom in Item 35 is from Herb Sutter's column, "Virtuality," in the September 2001 C/C++ Users 
Journal. In that same Item, the Template Method and Strategy design patterns are from Design Patterns 
(Addison-Wesley, 1995) by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. The idea of using 
the NVI idiom in Item 37 came from Hendrik Schober. David Smallberg contributed the motivation for writing a 
custom set implementation in Item 38. Item 39's observation that the EBO generally isn't available under 
multiple inheritance is from David Vandevoorde's and Nicolai M. Josuttis' C++ Templates (Addison-Wesley, 
2003). In Item 42, my initial understanding about typename came from Greg Comeau's C++ and C FAQ (http://
www.comeaucomputing.com/techtalk/#typename), and Leor Zolman helped me realize that my understanding 
was incorrect. (My fault, not Greg's.) The essence of Item 46 is from Dan Saks' talk, "Making New Friends." The 
idea at the end of Item 52 that if you declare one version of operator new, you should declare them all, is 
from Item 22 of Herb Sutter's Exceptional C++ Style. My understanding of the Boost review process 
(summarized in Item 55) was refined by David Abrahams.
Everything above corresponds to who or where I learned about something, not necessarily to who or where the 
thing was invented or first published.
My notes tell me that I also used information from Steve Clamage, Antoine Trux, Timothy Knox, and Mike 
Kaelbling, though, regrettably, the notes fail to tell me how or where.
file:///D|/work/material/C++/Effective%20C++%203rd.Edition/0321334876/pref04.html（第 1／3 页）2009-1-9 14:36:30

Acknowledgments

Drafts of the first edition were reviewed by Tom Cargill, Glenn Carroll, Tony Davis, Brian Kernighan, Jak

Kirman, Doug Lea, Moises Lejter, Eugene Santos, Jr., John Shewchuk, John Stasko, Bjarne Stroustrup, Barbara

Tilly, and Nancy L. Urbano. I received suggestions for improvements that I was able to incorporate in later

printings from Nancy L. Urbano, Chris Treichel, David Corbin, Paul Gibson, Steve Vinoski, Tom Cargill, Neil

Rhodes, David Bern, Russ Williams, Robert Brazile, Doug Morgan, Uwe Steinmüller, Mark Somer, Doug

Moore, David Smallberg, Seth Meltzer, Oleg Shteynbuk, David Papurt, Tony Hansen, Peter McCluskey, Stefan

Kuhlins, David Braunegg, Paul Chisholm, Adam Zell, Clovis Tondo, Mike Kaelbling, Natraj Kini, Lars Nyman,

Greg Lutz, Tim Johnson, John Lakos, Roger Scott, Scott Frohman, Alan Rooks, Robert Poor, Eric Nagler,

Antoine Trux, Cade Roux, Chandrika Gokul, Randy Mangoba, and Glenn Teitelbaum.

Drafts of the second edition were reviewed by Derek Bosch, Tim Johnson, Brian Kernighan, Junichi Kimura,

Scott Lewandowski, Laura Michaels, David Smallberg, Clovis Tondo, Chris Van Wyk, and Oleg Zabluda. Later

printings benefited from comments from Daniel Steinberg, Arunprasad Marathe, Doug Stapp, Robert Hall,

Cheryl Ferguson, Gary Bartlett, Michael Tamm, Kendall Beaman, Eric Nagler, Max Hailperin, Joe Gottman,

Richard Weeks, Valentin Bonnard, Jun He, Tim King, Don Maier, Ted Hill, Mark Harrison, Michael Rubenstein,

Mark Rodgers, David Goh, Brenton Cooper, Andy Thomas-Cramer, Antoine Trux, John Wait, Brian Sharon,

Liam Fitzpatrick, Bernd Mohr, Gary Yee, John O'Hanley, Brady Patterson, Christopher Peterson, Feliks

Kluzniak, Isi Dunietz, Christopher Creutzi, Ian Cooper, Carl Harris, Mark Stickel, Clay Budin, Panayotis

Matsinopoulos, David Smallberg, Herb Sutter, Pajo Misljencevic, Giulio Agostini, Fredrik Blomqvist, Jimmy

Snyder, Byrial Jensen, Witold Kuzminski, Kazunobu Kuriyama, Michael Christensen, Jorge Yáñez Teruel, Mark

Davis, Marty Rabinowitz, Ares Lagae, and Alexander Medvedev.

An early partial draft of this edition was reviewed by Brian Kernighan, Angelika Langer, Jesse Laeuchli, Roger

E. Pedersen, Chris Van Wyk, Nicholas Stroustrup, and Hendrik Schober. Reviewers for a full draft were Leor

Zolman, Mike Tsao, Eric Nagler, Gene Gutnik, David Abrahams, Gerhard Kreuzer, Drosos Kourounis, Brian

Kernighan, Andrew Kirmse, Balog Pal, Emily Jagdhar, Eugene Kalenkovich, Mike Roze, Enrico Carrara,

Benjamin Berck, Jack Reeves, Steve Schirripa, Martin Fallenstedt, Timothy Knox, Yun Bai, Michael Lanzetta,

Philipp Janert, Guido Bartolucci, Michael Topic, Jeff Scherpelz, Chris Nauroth, Nishant Mittal, Jeff Somers, Hal

Moroff, Vincent Manis, Brandon Chang, Greg Li, Jim Meehan, Alan Geller, Siddhartha Singh, Sam Lee, Sasan

Dashtinezhad, Alex Marin, Steve Cai, Thomas Fruchterman, Cory Hicks, David Smallberg, Gunavardhan

Kakulapati, Danny Rabbani, Jake Cohen, Hendrik Schober, Paco Viciana, Glenn Kennedy, Jeffrey D. Oldham,

Nicholas Stroustrup, Matthew Wilson, Andrei Alexandrescu, Tim Johnson, Leon Matthews, Peter Dulimov, and

Kevlin Henney. Drafts of some individual Items were reviewed by Herb Sutter and Attila F. Feher.

Reviewing an unpolished (possibly incomplete) manuscript is demanding work, and doing it under time pressure

only makes it harder. I continue to be grateful that so many people have been willing to undertake it for me.

Reviewing is harder still if you have no background in the material being discussed and are expected to catch

every problem in the manuscript. Astonishingly, some people still choose to be copy editors. Chrysta

Meadowbrooke was the copy editor for this book, and her very thorough work exposed many problems that

eluded everyone else.

Leor Zolman checked all the code examples against multiple compilers in preparation for the full review, then

did it again after I revised the manuscript. If any errors remain, I'm responsible for them, not Leor.

file:///D|/work/material/C++/Effective%20C++%203rd.Edition/0321334876/pref04.html（第 2／3 页）2009-1-9 14:36:30

Acknowledgments

Karl Wiegers and especially Tim Johnson offered rapid, helpful feedback on back cover copy.

John Wait, my editor for the first two editions of this book, foolishly signed up for another tour of duty in that

capacity. His assistant, Denise Mickelsen, adroitly handled my frequent pestering with a pleasant smile. (At least

I think she's been smiling. I've never actually seen her.) Julie Nahil drew the short straw and hence became my

production manager. She handled the overnight loss of six weeks in the production schedule with remarkable

equanimity. John Fuller (her boss) and Marty Rabinowitz (his boss) helped out with production issues, too.

Vanessa Moore's official job was to help with FrameMaker issues and PDF preparation, but she also added the

entries to Appendix B and formatted it for printing on the inside cover. Solveig Haugland helped with index

formatting. Sandra Schroeder and Chuti Prasertsith were responsible for cover design, though Chuti seems to

have been the one who had to rework the cover each time I said, "But what about this photo with a stripe of that

color...?" Chanda Leary-Coutu got tapped for the heavy lifting in marketing.

During the months I worked on the manuscript, the TV series Buffy the Vampire Slayer often helped me "de-

stress" at the end of the day. Only with great restraint have I kept Buffyspeak out of the book.

Kathy Reed taught me programming in 1971, and I'm gratified that we remain friends to this day. Donald French

hired me and Moises Lejter to create C++ training materials in 1989 (an act that led to my really knowing C++),

and in 1991 he engaged me to present them at Stratus Computer. The students in that class encouraged me to

write what ultimately became the first edition of this book. Don also introduced me to John Wait, who agreed to

publish it.

My wife, Nancy L. Urbano, continues to encourage my writing, even after seven book projects, a CD adaptation,

and a dissertation. She has unbelievable forbearance. I couldn't do what I do without her.

From start to finish, our dog, Persephone, has been a companion without equal. Sadly, for much of this project,

her companionship has taken the form of an urn in the office. We really miss her.

< Day Day Up >

file:///D|/work/material/C++/Effective%20C++%203rd.Edition/0321334876/pref04.html（第 3／3 页）2009-1-9 14:36:30

Introduction

< Day Day Up >

Introduction

Learning the fundamentals of a programming language is one thing; learning how to design and implement

effective programs in that language is something else entirely. This is especially true of C++, a language boasting

an uncommon range of power and expressiveness. Properly used, C++ can be a joy to work with. An enormous

variety of designs can be directly expressed and efficiently implemented. A judiciously chosen and carefully

crafted set of classes, functions, and templates can make application programming easy, intuitive, efficient, and

nearly error-free. It isn't unduly difficult to write effective C++ programs, if you know how to do it. Used without

discipline, however, C++ can lead to code that is incomprehensible, unmaintainable, inextensible, inefficient, and

just plain wrong.

The purpose of this book is to show you how to use C++ effectively. I assume you already know C++ as a

language and that you have some experience in its use. What I provide here is a guide to using the language so

that your software is comprehensible, maintainable, portable, extensible, efficient, and likely to behave as you

expect.

The advice I proffer falls into two broad categories: general design strategies, and the nuts and bolts of specific

language features. The design discussions concentrate on how to choose between different approaches to

accomplishing something in C++. How do you choose between inheritance and templates? Between public and

private inheritance? Between private inheritance and composition? Between member and non-member functions?

Between pass-by-value and pass-by-reference? It's important to make these decisions correctly at the outset,

because a poor choice may not become apparent until much later in the development process, at which point

rectifying it is often difficult, time-consuming, and expensive.

Even when you know exactly what you want to do, getting things just right can be tricky. What's the proper

return type for assignment operators? When should a destructor be virtual? How should operator new

behave when it can't find enough memory? It's crucial to sweat details like these, because failure to do so almost

always leads to unexpected, possibly mystifying program behavior. This book will help you avoid that.

This is not a comprehensive reference for C++. Rather, it's a collection of 55 specific suggestions (I call them

Items) for how you can improve your programs and designs. Each Item stands more or less on its own, but most

also contain references to other Items. One way to read the book, then, is to start with an Item of interest, then

follow its references to see where they lead you.

The book isn't an introduction to C++, either. In Chapter 2, for example, I'm eager to tell you all about the proper

implementations of constructors, destructors, and assignment operators, but I assume you already know or can go

elsewhere to find out what these functions do and how they are declared. A number of C++ books contain

information such as that.

The purpose of this book is to highlight those aspects of C++ programming that are often overlooked. Other

books describe the different parts of the language. This book tells you how to combine those parts so you end up

with effective programs. Other books tell you how to get your programs to compile. This book tells you how to

file:///D|/work/material/C++/Effective%20C++%203rd.Edition/0321334876/pref05.html（第 1／2 页）2009-1-9 14:36:31

剩余472页未读，继续阅读

tiansun504

粉丝: 1
资源: 1

Effective C++ 3rd Edition：提升C++程序设计与优化的55个具体方法

effective c++ 3rd英文版

effective C++ 3rd edition

Effective C++ 3rd Edition英文版

Effective C++ 3rd Edition 英文版 CHM格式

Effective C++3rd中文版.part1

Effective C++3rd中文版.part3

Effective C++3rd中文版.part2

effective c++ 3rd

Effective C++ 3rd en

Effective C++ 3rd Edition

最新资源