C++ Coding Standards: 101 Rules, Guidelines, and Best Practices > Don’t use invalid objects. Don’t use unsafe functions > Summary

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

Construction, Destruction, and Copying

Namespaces and Modules

Templates and Genericity

Error Handling and Exceptions

STL: Containers

STL: Algorithms

Type Safety

Ch. 90. Avoid type switching; prefer polymorphism

Ch. 91. Rely on types, not on representations

Ch. 92. Avoid using reinterpret_cast

Ch. 93. Avoid using static_cast on pointers

Ch. 94. Avoid casting away const

Ch. 95. Don’t use C-style casts

Ch. 96. Don’t memcpy or memcmp non-PODs

Ch. 97. Don’t use unions to reinterpret representation

Ch. 98. Don’t use varargs (ellipsis)

Ch. 99. Don’t use invalid objects. Don’t use unsafe functions

Summary

Discussion

References

Ch. 100. Don’t treat arrays polymorphically

Bibliography

Summary of Summaries

Index

Summary

Don’t use expired medicines: Both invalid objects and historical but unsafe functions wreak havoc on your program’s health.

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 99. Don’t use invalid objects. Don’t use unsafe functions > Summary

Summary