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):||28 December 2006|
|PDF File Size:||7.38 Mb|
|ePub File Size:||15.12 Mb|
|Price:||Free* [*Free Regsitration Required]|
C++ Coding Standards: 101 Rules, Guidelines, and Best Practices by Andrei Alexandrescu, Herb Sutter
Prefer composition to inheritance. But beware the trap of being too quick to think: What rules should you follow to ensure type-safe code?
If you apexandrescu any class-specific new, provide all of the standard forms plain, in-place, and nothrow. Make data members private, except in behaviorless aggregates C-stylestructs. Prefer minimal classes to monolithic classes. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.
Error Handling and Exceptions. Distinguish between errors and non-errors. But this book is something more: This happens automatically when following a good, simple set of guidelines.
Correctness, simplicity, and clarity come first. Use the right STL search algorithm. Declare variables as locally slexandrescu possible. Use the right STL sort algorithm. Prefer compile- and link-time errors to run-time errors Prefer calling the prefix forms Avoid providing implicit conversions Report, handle, and translate errors appropriately Destructors, deallocation, and swap never fail Consider alexandredcu virtual functions nonpublic, and public functions nonvirtual.
Invest in code reviews. Each standard is described concisely, with practical examples. Prefer to use exceptions to report errors Book Description Consistent, high-quality coding standards improve software quality, reduce time-to-market, promote teamwork, eliminate time wasted on inconsequential matters, and simplify foding.
Don’t treat arrays polymorphically. Use explicit RAII and smart pointers. Know when and how to code for concurrency.
Prefer providing abstract interfaces. Any and usually rare cases when a rule doesn’t apply. Otherwise, choose an appropriate container. Don’t use invalid objects.
Assert liberally to document internal assumptions and invariants. Use an automated build system 3. Public inheritance is substitutability.
C++ Coding Standards: 101 Rules, Guidelines, and Best Practices
Sign In We’re sorry! Always provide new and delete together. Avoid allocating and deallocating memory standares different modules.
Make predicates pure functions Be clear what kind of class you’re writing. Know when and how to code for scalability. Algorithms; and Type Safety. Design and write error-safe code Use vector by default. Give one entity one cohesive responsibility. Copy and destroy consistently Avoid magic numbers Keep a type and its nonmember function interface in the same namespace.
Ensure resources are owned by objects.
Use const proactively – C++ Coding Standards: Rules, Guidelines, and Best Practices [Book]
Use an automated build system. Prefer compile- and link-time errors to run-time errors. Always initialize variables Declare variables as locally as possible.