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):||2 February 2017|
|PDF File Size:||11.55 Mb|
|ePub File Size:||20.36 Mb|
|Price:||Free* [*Free Regsitration Required]|
Always initialize codlng When and how should you use static and dynamic polymorphism together? Don’t sweat the small stuff. Preview this title online. Avoid magic numbers What are the elements of a rational error handling policy? Prefer minimal classes to monolithic classes. Make header files self-sufficient.
Sutter & Alexandrescu, C++ Coding Standards: Rules, Guidelines, and Best Practices | Pearson
Know when and how to code for concurrency. When should you provide a no-fail swap?
Use the right STL sort algorithm Report, handle, and translate errors appropriately. Take parameters appropriately by value, smart pointer, or reference. About the Author s. You have never seen a book quite like this before.
C++ Coding Standards: Rules, Guidelines, and Best Practices [Book]
Don’t use unions to reinterpret representation. Rely on types, not on standarsd. With Safari, you learn the way you learn best. Avoid providing implicit conversions. Prefer range operations to single-element operations. Establish a rational error handling policy, and follow it strictly. Avoid allocating and deallocating memory in different modules.
Avoid suttter dependencies across compilation units Minimize global and shared data Throw by value, catch by reference Stay ahead with the world’s most comprehensive technology and business learning platform. Always provide new and delete together.
C++ Coding Standards: 101 Rules, Guidelines, and Best Practices by Andrei Alexandrescu, Herb Sutter
Avoid providing implicit conversions Don’t use unsafe functions. Why should you use STL vector and string instead of arrays? The Legend of Zelda: Use the right STL search algorithm. Prefer providing abstract interfaces Keep a type and its nonmember function interface in the same namespace. Prefer to use exceptions to report errors Error Handling and Exceptions.
Prefer the canonical form of assignment. Prefer range operations to single-element operations. How do you practice “safe” overriding? Organizational and Policy Issues. Inherit, not to reuse, but to be reused Inherit, not to reuse, but to be reused.
Keep types and functions in separate namespaces unless they’re specifically intended to work together. Write function objects correctly. Prefer calling the prefix forms.
C++ Coding Standards: 101 Rules, Guidelines, and Best Practices
Signed out You have successfully signed out and will be required to sign dutter in should you need to download more resources. Construction, Destruction, and Copying. Always write internal include guards.
Prefer composition to inheritance.