C++编程规范（英文版）——图灵原版计算机科学系列 (2008 年度畅销榜NO.918 )

在本书中，两位知名的C++专家将全球C++团体的集体智慧和经验凝结成一套编程规范。这些规范可以作为每一个开发团队制定实际开发规范的基础，更是每一位C++程序员应该遵循的行事准则。书中对每一条规范都给出了精确的描述，并辅以实例说明；从类型定义到差错处理，都给出了最佳的C++实践。即使使用C++多年的程序员也会从中受益匪浅。 \r\n　　本书适合于各层次C++程序员，也可作为高等院校C++课程的教学参考书。

Organizational and Policy Issues　1\r\n0. Don''t sweat the small stuff. (Or: Know what not to standardize.)　2\r\n1. Compile cleanly at high warning levels.　4 \r\n2. Use an automated build system.　7\r\n3. Use a version control system.　8\r\n4. Invest in code reviews.　9\r\n\r\nDesign Style　　11\r\n5. Give one entity one cohesive responsibility.　12\r\n6. Correctness, simplicity, and clarity come first.　13\r\n7. Know when and how to code for scalability.　14\r\n8. Don''t optimize prematurely.　16\r\n9. Don''t pessimize prematurely.　18\r\n10. Minimize global and shared data.　19\r\n11. Hide information.　20\r\n12. Know when and how to code for concurrency.　21\r\n13. Ensure resources are owned by objects. Use explicit RAII and smart pointers.　24\r\n\r\nCoding Style　27\r\n14. Prefer compile- and link-time errors to run-time errors.　28\r\n15. Use const proactively.　30\r\n16. Avoid macros.　32\r\n17. Avoid magic numbers.　34\r\n18. Declare variables as locally as possible.　35\r\n19. Always initialize variables.　36\r\n20. Avoid long functions. Avoid deep nesting.　38\r\n21. Avoid initialization dependencies across compilation units.　 39\r\n22. Minimize definitional dependencies. Avoid cyclic dependencies.　40\r\n23. Make header files self-sufficient.　42\r\n24. Always write internal #include guards. Never write external #include guards.　43\r\n\r\nFunctions and Operators　45 \r\n25. Take parameters appropriately by value, (smart) pointer, or reference.　46\r\n26. Preserve natural semantics for overloaded operators.　47\r\n27. Prefer the canonical forms of arithmetic and assignment operators.　48\r\n28. Prefer the canonical form of + + and --. Prefer calling the prefix forms.　50\r\n29. Consider overloading to avoid implicit type conversions.　51\r\n30. Avoid overloading &&, ￠ò, or, (comma).　52\r\n31. Don''t write code that depends on the order of evaluation of function arguments.　54\r\n　\r\nClass Design and Inheritance　55\r\n32. Be clear what kind of class you'' re writing.　56\r\n33. Prefer minimal classes to monolithic classes.　57\r\n34. Prefer composition to inheritance.　58\r\n35. Avoid inheriting from classes that were not designed to be base classes.　60\r\n36. Prefer providing abstract interfaces.　62\r\n37. Public inheritance is substitutability. Inherit, not to reuse, but to be reused　64\r\n38. Practice safe overriding.　66\r\n39. Consider making virtual functions nonpublic, and public functions nonvirtual.　68\r\n40. Avoid providing implicit conversions.　70\r\n41. Make data members private, except in behaviorless aggregates (C-style structs).　72　\r\n42. Don''t give away your internals.　74\r\n43. Pimpl judiciously.　76\r\n44. Prefer writing nonmember nonfriend functions.　79\r\n45. Always provide new and delete together.　80\r\n46. If you provide any class-specific new, provide all of the standard forms (plain, in-place, and nothrow).　82 \r\n\r\nConstruction, Destruction, and Copying　85\r\n47. Define and initialize member variables in the same order.　86\r\n48. Prefer initialization to assignment in constructors.　87\r\n49. Avoid calling virtual functions in constructors and destructors.　88\r\n50. Make base class destructors public and virtual, or protected and nonvirtual.　90\r\n51. Destructors, deallocation, and swap never fail.　92\r\n52. Copy and destroy consistently.　93\r\n53. Explicitly enable or disable copying.　95\r\n54. Avoid slicing. Consider Clone instead of copying in base classes.　96\r\n55. Prefer the canonical form of assignment.　99\r\n56. Whenever it makes sense, provide a no-fail swap (and provide it correctly).　100\r\n\r\nNamespaces and Modules　103\r\n57. Keep a type and its nonmember function interface in the same namespace.　104\r\n58. Keep types and functions in separate namespaces unless they''re specifically intended to work together.　106\r\n59. Don''t write namespace usings in a header file or before an #include.　108\r\n60. Avoid allocating and deallocating memory in different modules.　111\r\n61. Don''t define entities with linkage in a header file.　112\r\n62. Don''t allow exceptions to propagate across module boundaries.　114\r\n63. Use sufficiently portable types in a module''s interface.　116\r\n\r\nTemplates and Genericity　119\r\n64. Blend static and dynamic polymorphism judiciously.　120\r\n65. Customize intentionally and explicitly.　122\r\n66. Don''t specialize function templates.　126\r\n67. Don''t write unintentionally nongeneric code.　128\r\n\r\nError Handling and Exceptions　129\r\n68. Assert liberally to document internal assumptions and invariants.　130\r\n69. Establish a rational error handling policy, and follow it strictly.　132\r\n70. Distinguish between errors and non-errors.　134\r\n71. Design and write error-safe code.　137\r\n72. Prefer to use exceptions to report errors.　140\r\n73. Throw by value, catch by reference.　144\r\n74. Report, handle, and translate errors appropriately.　145\r\n75. Avoid exception specifications.　146\r\n\r\nSTL: containers　149\r\n76. Use vector by default. Otherwise, choose an appropriate container.　150\r\n77. Use vector and string instead of arrays.　152\r\n78. Use vector (and string::c_str) to exchange data with non-C++ APIs.　153\r\n79. Store only values and smart pointers in containers.　154\r\n80. Prefer pushback to other ways of expanding a sequence.　155\r\n81. Prefer range operations to single-element operations.　156\r\n82. Use the accepted idioms to really shrink capacity and really erase elements.　157\r\n\r\nSTL: Algorithms　159\r\n83. Use a checked STL implementation.　160\r\n84. Prefer algorithm calls to handwritten loops.　162\r\n85. Use the right STL search algorithm.　165\r\n86. Use the right STL sort algorithm.　166\r\n87. Make predicates pure functions.　68\r\n88. Prefer function objects over functions as algorithm and comparer arguments.　170\r\n89. Write function objects correctly.　172\r\n\r\nType Safety　173\r\n90. Avoid type switching; prefer polymorphism.　174\r\n91. Rely on types, not on representations.　176\r\n92. Avoid using reinterpret_cast.　177\r\n93. Avoid using static_cast on pointers.　178\r\n94. Avoid casting away const.　179\r\n95. Don''t use C-style casts.　180\r\n96. Don''t memcpy or memcmp non-PODs.　182\r\n97. Don''t use unions to reinterpret representation.　183\r\n98. Don''t use varargs (ellipsis).　184\r\n99. Don''t use invalid objects. Don''t use unsafe functions.　185\r\n100.　Don''t treat arrays polymorphically.　186\r\n\r\nBibliography　187\r\nSummary of Summaries　195\r\nIndex　209

Herb Sutter ISO C++标准委员会主席，C++ USERS JOURNAL杂志特邀编辑和专栏作家。他目前在微软公司领导.NET环境下C++语言扩展的设计工作。除本收外，他还撰写了三本广受赞誉的图书：EXCEPTIONAL ++ STYLE、EXCEPTIONAL C++和MORE EXCEPTIONAL C++。
Andrei Alexandrescu 世界顶尖的C++专家，C++ USERS JOURNAL杂志的专栏作家，他的MOD-ERN C++ DESING一书曾荣获2001年最佳C++图书称号。书中所开发的LOKI已经成为最负盛名的C++程序库之一。