C++ Coding Standards by Herb Sutter and Andrei Alexandrescu, the newest book in Bjarne Stroustrup’s C++ In Depth series, is the authoritative ebook reference for C++ software development teams. It’s the only C++ coding standard with Stroustrup’s name on it, and the only one book written by two of the top names C++. Both authors draw on their personal extensive real-world project experience at commercial software companies ranging in size from small successful start-ups to RealNetworks to Microsoft. That concrete, in-the-trenches experience shines through in Item after Item as the book covers not only many issues of note in Standard C++ itself, but also includes important material on how Standard C++ interacts with nonstandard but real-world topics like dealing with threading and concurrency, handling application scalability, and correctly designing and deploying modules (including shared libraries and DLLs).
Overview: This ebook delivers a valuable set of tried-and-true rules, guidelines, and best practices condensed into 101 concise one- and two-page Items. But this book is something more: It also acts as an index into the world’s C++ literature because each Item includes copious references that, in all, cite nearly 100 different top books and articles—from Brooks’ classic The Mythical Man-Month to Vandevoorde and Josuttis’ cutting-edge C++ Templates to the authors’ own previous books—and distill the scattered advice and guidelines into one authoritative handbook.
Book contents: The topical sections it covers are:
- Organizational and Policy Issues;
- Design Style;
- Coding Style;
- Functions and Operators;
- Class Design and Inheritance;
- Book describes Construction, Destruction, and Copying;
- Namespaces and Modules;
- EBook contains description of Templates and Genericity;
- Error Handing and Exceptions;
- STL: Containers;
- STL: Algorithms;
- Type Safety
Each Item of the ebook is laid out as follows:
Item title: The simplest meaningful sound bite we could come up with as a mnemonic for the rule.
Summary: The most essential points, briefly stated.
Discussion: An extended explanation of the guideline. This often includes brief rationale, but remember that the bulk of the rationale is intentionally left in the References.
Examples (if applicable): Examples that demonstrate a rule or make it memorable.
Exceptions (if applicable): Any (and usually rare) cases when a rule doesn’t apply. But beware the trap of being too quick to think: “Oh, I’m special; this doesn’t apply in my situation” — that rationalization is common, and commonly wrong.
References: See these parts of the C++ books for the full details and analysis.
A landmark book that belongs on every C++ development team’s bookshelf and reading list.
Entries (RSS)
i need this copy
Comment by deipti — March 27, 2010 @ 4:23 am