| Type |
Page |
Error |
Correction |
Reported By |
| Aesthetic |
21 |
The chapter title "Holy Wars: Programming
Standards--Causes and Cures"
is not my preferred title! |
The chapter was originally called "Holy Wars", which
I happen to think is a better title. I was overruled. Never write
your first book. Go straight onto your second. |
| Typographical |
27 |
Paragraph entitled 'Whitespace Around Tokens' |
There should really be a page break here, to keep the
following source code on one page. |
| Typographical |
29 |
'Djikstra' (two occurrences) |
Should of course be 'Dijkstra' - oops! |
| Typographical |
37 |
'0x80000000' (two occurrences) |
Should be printed in monospace font. |
| Typographical |
37 |
Quote from Standard isn't sufficiently distinct
from rest of text. |
Should be in a different font (e.g. italic),
and preferably with wider margins on each side. |
| Typographical |
38 |
NULL |
Should be printed in monospace font. |
| Technical |
38 |
"The programmer needs a new integer" |
Actually, the programmer needs a new double!
Change 'integer' to either 'number' or 'value'. |
Chris Mears (and Ben Pfaff spotted it too). Chris actually
pointed out later on that I'd got the erratum wrong,
but I've now corrected it. (And Dave V spotted it too. Looks
like a popular error...) |
| Typographical |
40 |
'there's only one stack so we can' is missing a comma |
'there's only one stack, so we can' |
| Typographical |
43 |
"str", "is", "to",
"mem", "SIG" |
Should be printed in monospace font,
without quotation marks. |
| Typographical |
49 |
Missing page break means comment box is split across pages. |
Insert page break. |
| Technical |
50 |
Cut and paste monster strikes again! The description of the minimalist comment is wrong. |
Replace description with 'This is a boxed comment with the box shape implied.' |
| Technical |
50 |
asterisk and hyphen |
Should be asterisk and slash |
Chris Mears |
|
| Typographical |
54 |
Quotes from Standard aren't sufficiently distinct from rest of text. |
Should be in a different font (e.g. italic), and preferably with wider margins on each side. |
| Typographical |
62 |
int should be in monospace font |
Change to int |
Chris Mears |
| Typographical |
62 |
"for example,q.foo.first.k" is all scrunched up. |
Insert some white space after the comma. |
Chris Mears |
| Typographical |
65 |
Quote from Standard isn't sufficiently distinct from rest of text. |
Should be in a different font (e.g. italic), and preferably with wider margins on each side. |
| Typographical |
66 |
Quote from Standard isn't sufficiently distinct from rest of text. |
Should be in a different font (e.g. italic), and preferably with wider margins on each side. |
| Typographical |
67 |
EOF |
Should be printed in monospace font. |
| Typographical |
69 |
long int, short int, char, short, int, and long are all given on this page in normal font. |
Should be printed in monospace font. |
| Typographical |
72 |
iostream |
Should be printed in monospace font. |
| Typographical |
73 |
char |
Should be printed in monospace font. |