Developers: Learn a New Programming Language or App Development with Deitel LiveLessons Videos!
s
menu
menu
Login  |  Register  |  Media Kit  |  Press  |  Contact Us  |   Twitter Become a Deitel Fan on Facebook  
Custom Search
 
AddThis Social Bookmark Button

Errata: C How to Program, 3/e

We wish to thank our many readers who took the time to email us with errata. If you find errata not listed on this page, please email us at deitel@deitel.com. Remember to include the book title and edition.


Note: You can determine which printing you have by looking at the bottom of the back of the second physical page in the book (page iv, but it has no page number). Just above the ISBN number is a list of numbers. For the first printing of the book, the list appears as follows:

    10 9 8 7 6 5 4 3 2 1

The last number in the list is the printing number. So the above list indicates printing 1 and the following list indicates printing 2:

    10 9 8 7 6 5 4 3 2

Chapter 1
  • p. 32: In our discussions of operator precedence, the numbers indicating precedence under the following expression

    z = p * r % q + w / x - y;
    are out of place. The should appear as follows

    z = p * r % q + w / x - y;

    6   1   2   4   3   5  

  • p. 27, Good Programming Practice 1.12: The word "abd" should be "and"
Chapter 2
  • p. 92, Fig. 2.18: In the for structure header, the word "var" should be "int."
  • p. 98, Fig. 2.21, Line 30: Keywords for and int should be colored blue.
  • p. 108, Fig. 2.27, Line 1: The comment should indicate the file name as fig02_27.cpp.
  • p. 112, Fig. 2.31: The unary ! operator is missing from the 3rd line of the operator precedence chart.
Chapter 4
  • p. 261, Fig. 4.15, Line 13: The characters "ssss" accidentally got inserted during final production. They are not part of the program and will generate a syntax error if the program is compiled with them. The program IS CORRECT on the CD-ROM that accompanies the book.
  • p. 259. The function prototype
          void modifyArray( int anyArrayName[], int anyVariableName )
    just above Good Programming Practice 4.3 should end with a semicolon.
Chapter 5
  • p. 338, last line: The function name bubbleSort should be bubble.
Chapter 6
  • p. 393, just above Fig. 6.1: The \ is a typo. It should be removed.
  • p. 415, top of page: The \ is a typo. It should be removed.
  • p. 416, Fig. 6.8, time2.cpp, part 2 of 2: The line numbers on this page should start with 46 and the remaining lines of the program should all be adjusted accordingly.
  • p. 423, Fig. 6.10 figure caption: The file name should be time3.h.
Chapter 7
  • There are two sections numbered 7.10. The second one should be 7.11.
Chapter 11
  • p. 666, Fig. 11.7, line 13: The ' character after the closing } curly brace should be deleted. The source code file for the program is correct.
  • p. 669, Fig. 11.9, part 2 of 2: The line numbers in this part of the program should start from 14 (not 1).
  • p. 682, Fig. 11.21, line 13: No functions of the <cmath> library are used in this program, so this line can be removed. Also, the figure caption of this example should indicate double values not float values (floating-point literals are of type double in C++).
  • p. 692, Fig. 11.29: After the bad input operation, the result of cin.fail() is 1 not 0 and the result of cin.good() is 0 not 1 as shown in the output window in the book.
Chapter 14
  • p. 773, 18th line of text from top of page: sizeo/f should be sizeof.
  • p. 775, Fig. 14.12, figure caption: The figure caption should state "Writing data randomly to a random-access file."
  • p. 779, Fig. 14.14, lines 51 and 52: The keywords reinterpret_cast, char and sizeof should appear in blue.
  • p. 800, Fig. 15.3--list.h: There is an extra period at the end of the figure caption in each of the 4 parts to this figure.
Chapter 15
  • p. 802, Fig. 15.3, lines 116 and 136 should say

    return false;

    the code is correct on disk.
  • p. 802, Fig. 15.3, lines 127 and 154 should say

    return true;

    the code is correct on disk.
Chapter 16
  • p. 872, Fig. 16.18, lines 31, 33, 35 and 37: The keywords static_cast and char should be colored blue.
  • p. 886, Fig. 16.36, line 16: The keywords static_cast and char should be colored blue.
  • p. 888, Fig. 16.38, line 16: The keywords static_cast and char should be colored blue.
  • p. 888, Fig. 16.39, line 16: The keywords static_cast and char should be colored blue.
Chapter 18
  • p. 929, Fig. 18.7, lines 14 and 18: The keyword goto should be colored blue.
Chapter 20
  • p. 1053, Fig. 20.42, line 16: The two int keywords in the parameter list should be colored blue.
  • p. 1054, Fig. 20.42, line 47: The keyword int should be colored blue.
Chapter 21
  • p. 1069, Fig. 21.1, line 28: The word boolean should not be in blue. It is not a keyword; rather it is the name of a variable of data type bool.
  • p. 1081, Fig. 21.7, line 63: The program works as is; however, the pointer name should be cylinderPtr not shapePtr.

Discounts on SafariBooksOnline.com subscriptions

 
C++ How to Program, 3/e Cover


ISBN: 0130895717
© 2001

Order now at
Amazon.com
Informit.com

C++ How to Program, 3/e
Download Code
Examples and
Other Premium
Content for
Registered Users

Login or Register to download this book's code examples and other premium content.

foot
Update :: December 16, 2017