Well, people certainly have a lot of time on their hands. I haven't read the
book in question, but the first few pages of
word minutiae. I can only imagine it is a beginners book and not actually
designed to split standards hairs. Now I won't recommend it or anything, but
the list of trivia on the web site for a first programming book was amazing.
Has this guy seen my 3rd grade science book?
Examples of things I don't care about in my first program, the authors
comments are prefaced by ##, with the idiot nitpicker following (my comments
begin with Huh?)
## No other keywords are allowed in a conforming program.
Of course, no other keywords are allowed in a strictly conforming program.
Huh? What does this even mean _strictly_ speaking.
## x = 'A'; /* give x the value 65 */
This comment, and the following text, leave the reader believing that 'A'
must have the value 65, and by extension that C requires the use of ASCII
codes. This is of course false, but it would be hard to tell from the book.
Huh? ^2 I'm trying to print "Hello, World!" - Do I need EBCDIC vs ASCII
## First, the null character may not be used except
## in the first byte of a multibyte sequence.
I read this as meaning that the multibyte character <00><94> is legal while
the multibyte character <94><00> is not. In actual fact, the standard
states that a zero byte must not appear in any multibyte character other
than the null character (i.e. the end of string indicator).
Huh? Isn't that the first byte in a multibyte character? Who cares if a 94
comes after the null? Am I supposed to care about the garbage after my
string's null? No.
I got bored after that.