Chapter 14. Const Correctness

FAQ 14.01 How should pointer declarations be read?

FAQ 14.02 How can C++ programmers avoid making unexpected changes to objects?

FAQ 14.03 Does const imply runtime overhead?

FAQ 14.04 Does const allow the compiler to generate more efficient code?

FAQ 14.05 Is const correctness tedious?

FAQ 14.06 Why should const correctness be done sooner rather than later?

FAQ 14.07 What's the difference between an inspector and a mutator?

FAQ 14.08 When should a member function be declared as const?

FAQ 14.09 Does const apply to the object's bitwise state or its abstract state?

FAQ 14.10 When should const not be used in declaring formal parameters?

FAQ 14.11 When should const not be used in declaring a function return type?

FAQ 14.12 How can a "nonobservable" data member be updated within a const member function?

FAQ 14.13 Can an object legally be changed even though there is a const reference (pointer) to it?

FAQ 14.14 Does const_cast mean lost optimization opportunities?