C++ Coding Standards: 101 Rules, Guidelines, and Best Practices > Keep types and functions in separate namespaces unless they’re specifically intended to work together > References - Pg. : Safari Books Online

Table of Contents

Download Safari Books Online apps: Apple iOS | Android

Entire Site

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

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

Search

Contents

The C++ In-Depth Series

Organizational and Policy Issues

Functions and Operators

Class Design and Inheritance

Construction, Destruction, and Copying

Namespaces and Modules

Ch. 57. Keep a type and its nonmember function interface in the same namespace

Ch. 58. Keep types and functions in separate namespaces unless they’re specifically intended to work together

Ch. 59. Don’t write namespace usings in a header file or before an #include

Ch. 60. Avoid allocating and deallocating memory in different modules

Ch. 61. Don’t define entities with linkage in a header file

Ch. 62. Don’t allow exceptions to propagate across module boundaries

Ch. 63. Use sufficiently portable types in a module’s interface

Templates and Genericity

Error Handling and Exceptions

STL: Containers

STL: Algorithms

Summary of Summaries

URL

Help

References

[Stroustrup00] §10.3.2, §11.2.4 • [Sutter00] §34 • [Sutter02] §39-40

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