Editorial Reviews. From the Back Cover. Consistent, high-quality coding standards improve Guidelines, and Best Practices (C++ In-Depth Series) eBook: Andrei Alexandrescu, Herb Sutter: Kindle Store. Covers coding standards for C++. C++ Coding Standards: Rules, Guidelines, and Best Practices. Herb Sutter. Andrei Alexandrescu. © |Addison-Wesley Professional | Available. Consistent, high-quality coding standards improve software quality, reduce time- to-market, promote teamwork, eliminate by Andrei Alexandrescu, Herb Sutter.
|Published (Last):||20 December 2013|
|PDF File Size:||19.38 Mb|
|ePub File Size:||11.69 Mb|
|Price:||Free* [*Free Regsitration Required]|
C++ Coding Standards: 101 Rules, Guidelines, and Best Practices
How do you practice “safe” overriding? Make base class destructors public and virtual, or protected and nonvirtual.
What sfandards should you follow to ensure type-safe code? Until now, this body of knowledge has been available only as folklore or spread in bits and pieces throughout books. Take parameters appropriately by value, smart pointer, or reference Description Every software development team should have and follow a coding standard. Correctness, simplicity, and clarity come first.
C++ Coding Standards – Book Home Page
Consider making virtual functions nonpublic, and public functions nonvirtual Make header files self-sufficient. Organizational and Policy Issues. Use the right STL search algorithm. Avoid allocating suttrr deallocating memory in different modules.
C++ Coding Standards: Rules, Guidelines, and Best Practices [Book]
Minimize global and shared data. Prefer function objects over alxeandrescu as algorithm and comparer arguments Don’t use varargs ellipsis. Inherit, not to reuse, but to be reused. Establish a rational error handling policy, and follow it strictly.
C++ Coding Standards: 101 Rules, Guidelines, and Best Practices by Andrei Alexandrescu, Herb Sutter
Always write internal include guards. Why and how should you prevent exceptions from propagating aexandrescu module boundaries? The Legend of Zelda: Prefer minimal classes to monolithic classes.
Prefer compile- and link-time errors to run-time errors. Take parameters appropriately by value, smart pointer, or reference. How do you practice “safe” overriding? Consider overloading to avoid implicit type conversions.
Each standard is described concisely, with practical examples. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.
Know when and how to code for concurrency. Make data members private, alexanddrescu in behaviorless aggregates C-style structs. Don’t allow exceptions to propagate across module boundaries. Use explicit RAII and smart pointers.
Compile cleanly at high warning levels. Declare variables as locally as possible Make base class destructors public and virtual, or protected and nonvirtual Use the right STL sort algorithm