As an example of machine-generated literature it's pretty effective, but
you need to work on having it write meaningful content.
I find it very interesting, actually. Jones has created an excellent
reference to a great deal of literature on C. There are a great many
interesting comments on C's development and the Committee's decisions;
while some of that is available in the Rationale, there's a lot of new
information here, I believe. I appreciate the detailed comparisons
with C++ on a wide array of points, since I have to use C++ for some
projects and I know the C standard much better than the C++ one.
The book should come in handy for winning arguments; Jones' focus on
the economics of developing in C will carry weight with beancounters.
Some of the coding guidelines do look useful, particularly when Jones
cites studies to back them up.
And frankly I simply find a lot of it fascinating, even if it doesn't
seem to be immediately applicable - like the discussion on what
factors have been demonstrated as having little effect on source-
code readability (such as serif versus sans-serif typeface).
It's a pity it wasn't copyedited, though. Just in skimming it I
found a number of typos and there are occasional formatting issues.
