Practical C Programming

Errata for Practical C Programming

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. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date Submitted Date Corrected
Page 251
Example 15-8 code

The example code (as downloaded from O'Reilly: still does not work correctly. The program will not find the numbers 6 and 991 (the second and next-to-last elements in the array).

Note from the Author or Editor:
Reader is correct. Good catch. Change if (low >= high) to if (low > high)

Anonymous  Dec 29, 2009 
Page 253
Last paragraph

The sentence: "How do we force the debugger to stop only when part_number == 735?" should read "... only when point_number == 735?" (part_number changed to point_number).

Note from the Author or Editor:
part_number should be "point_number". (not the other way round).

Anonymous  Dec 29, 2009 
Page 291
First code snippet

First code snippet reads has a typo. The variable new_ptr should be new_item_ptr based on related examples in the book. Incorrect line: insert_ptr->previous_ptr->next_ptr = new_ptr Corrected line: insert_ptr->previous_ptr->next_ptr = new_item_ptr

Note from the Author or Editor:
Reader is correct.

Anonymous  Dec 31, 2009