Errata

C++ Pocket Reference

Errata for C++ Pocket Reference

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page 5
Termination section

"implicit return of 0 takes places" should be
"implicit return of 0 takes place"

 Steve Chapel  Jun 17, 2011 
Printed Page 15
Integer values section

The typical size for long is four bytes on 32-bit operating systems and eight bytes on 64-bit operating systems.

 Steve Chapel  Jun 29, 2011 
Printed Page 16
6th line from bottom

The word "double" is not in constant width font.

 Steve Chapel  Jun 15, 2011 
Printed Page 21
1st code example

The section showing how to pass arrays to functions has a small typo. It declares "int handles[]" however, the next line says "handle[0] = 0;" missing the 's' at the end.

Anonymous  Mar 10, 2011 
Printed Page 44
Bitwise AND, OR, and XOR section

The section on &, |, and ^ should explain that the precedence of these operators is lower than that of ==, so to test bit fields you must use parentheses, such as (n & 0x3) == 0x2

 Steve Chapel  Jul 14, 2011 
Printed Page 52
Declaring Functions section

The section Declaring Functions does not explain how to declare a function that uses a variable number of arguments.

 Steve Chapel  Aug 22, 2011 
Printed Page 53
Default arguments section

This section does not mention that polymorphism is not used when filling in default arguments. The base class method's default arguments are used, even if a derived class's method is called at runtime.

 Steve Chapel  Jun 29, 2011 
Printed Page 69
2nd paragraph

The book does not describe that an object-list may be included between the closing curly brace and the semicolon of a class, struct or union definition.

 falap  Dec 29, 2008 
Printed Page 82
last sentence in Copy contructors section

The sentence "When you define a copy constructor for a class, often you also overload the assignment operator." is a small part of the rule-of-three: "If a class defines any of 1) destructor, 2) copy constructor, or 3) assignment operator, then it should probably define all three."

 Steve Chapel  Jun 29, 2011 
Printed Page 84
Second paragraph

Just before the first code segment on the page (End of the 2nd paragraph) you put "The following example declares a constructor named ~Account:".
This should be "The following example declares a destructor named ~Account".

You put constructor where you meant destructor.
Horst

 Horst Lindner  Dec 15, 2011 
Printed Page 94
bullet items

The words on the last lines of the bullet items are run together.

 Steve Chapel  Jun 15, 2011 
Printed Page 107
"The following rules..." section

There is no description of the difference between overloading the pre- and post- increment and decrement operators. The book should explain which take an extra dummy argument.

 Steve Chapel  Jun 15, 2011