C Pocket Reference by Peter Prinz, Ulla Kirch-Prinz The following errata were *corrected* in the 6/05 reprint: Here's a key to the markup: [page-number]: serious technical mistake {page-number}: minor technical mistake : important language/formatting problem (page-number): language change or minor formatting problem (2) 1st paragraph; The URL for ordering copies of the ANSI standard HAS BEEN UPDATED to "http://webstore.ansi.org" {22} Title of the subsection; "Relational and Logical Operators" NOW READS: "Relational Operators" p. 24, IN PRINT: end of the second paragraph: "...values 0 or 1" NOW READS: "...values 1 or 0" [60] 1st sentence of 2nd paragraph Functions that are declared as static, however, can only be called in the same translation unit in which they are defined NOW READS: Functions that are declared as static, however, can only be called using their name in the same translation unit in which they are defined. {66} 5th paragraph, directive syntax; define name[(parameter_list)] replacement_text NOW READS: #define name[(parameter_list)] replacement_text p. 83, IN PRINT: first item in bulleted list, last sentence: "...as many decimal places as necessary..." NOW READS: "..as many hexadecimal numerals as necessary..." (83) 3rd line in the continuation of table 24; "P" NOW READS "p" p. 92, IN PRINT: end of first sentence of the first full paragraph: "...are also provided for integers of type long long(*)." NOW READS: "...are also provided for integers of type long or long long(*)." p. 102, IN PRINT: last line of the last paragraph: "...wctype() or wtrans():" NOW READS: "...wctype() or wctrans():" [104] 8 paragraph (function strncpy description); NOW READS: "Copies the first n characters of s2 to the char array s1. The string terminator character '\0' is not appended. If s2 is a string that is shorter than n characters, the remaining characters written are '\0'." p. 108, IN PRINT: end of mbstowcs() description: "...to the array addressed by s." NOW READS: "... to the array addressed by p." p. 109, IN PRINT: 4th line: "...for the keyword addressed by...". NOW READS: "...for the key addressed by..." p. 110, IN PRINT: 3rd line: "...every character is read..." NOW READS: "...every byte is read..." p. 119: IN PRINT: Two lines of comments below "char p_sep_by_space": // 1 = currency symbol is before, // 0 = after the amount (1) NOW READS: // 1 = space, 0 = no space // between currency // symbol and amount (0) AND three lines below "char int_p_cs_precedes": // 1=space, 0 = no space // between currency symbol // and amount (1) NOW READS: // 1 = currency symbol precedes // amount, 0 = currency symbol // follows amount (1)