C++ Coding Standards: 101 Rules, Guidelines, and Best Practices > Pimpl judiciously > Exceptions

Table of Contents

Download Safari Books Online apps: Apple iOS | Android

Entire Site

Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

This Book

C++ Coding Standards: 101 Rules, Guidelines, and Best Practices

Search

The C++ In-Depth Series

Preface

Organizational and Policy Issues

Design Style

Coding Style

Functions and Operators

Class Design and Inheritance

Ch. 32. Be clear what kind of class you’re writing

Ch. 33. Prefer minimal classes to monolithic classes

Ch. 34. Prefer composition to inheritance

Ch. 35. Avoid inheriting from classes that were not designed to be base classes

Ch. 36. Prefer providing abstract interfaces

Ch. 37. Public inheritance is substitutability. Inherit, not to reuse, but to be reused

Ch. 38. Practice safe overriding

Ch. 39. Consider making virtual functions nonpublic, and public functions nonvirtual

Ch. 40. Avoid providing implicit conversions

Ch. 41. Make data members private, except in behaviorless aggregates (C-style structs)

Ch. 42. Don’t give away your internals

Ch. 43. Pimpl judiciously

Ch. 44. Prefer writing nonmember nonfriend functions

Ch. 45. Always provide new and delete together

Ch. 46. If you provide any class-specific new, provide all of the standard forms (plain, in-place, and nothrow)

Construction, Destruction, and Copying

Namespaces and Modules

Templates and Genericity

Error Handling and Exceptions

Exceptions

Only add complexity, including Pimpls, when you know you benefit from the extra level of indirection. (See Items 6 and 8.)

You are currently reading a PREVIEW of this book.

Get instant access to over
$1 million worth of books and videos.

Start a Free Trial

Download Safari Books Online apps: Apple iOS | Android

This Book

Search

Contents

Chapter 43. Pimpl judiciously > Exceptions

Exceptions