S
spinoza1111
You're lying: you posted none. I was the one with the questions about
"C: the Complete Reference". I pointed out its contradictions:
"The following is a partial list [1] of the errors I am aware of [2],
sorted by page number. I am not including everything [3]; just many
[4] of them."
"I am missing several hundred errors [5]. Please write me if you think
you know of any I'm missing. [6] Please also write if you believe one
of these corrections is inadequate or wrong; I'd love to see it."
"Currently known: [5]"
[1] Contradicts "currently known". Like your solecism in the use of
"clear", which means understandable and providing a clear view of the
truth, your sloppy English allows you to lie to yourself and others.
"Currently known" means in the absence of further qualification,
"these are all the known errors".
[2] Implies that there are n errors and the list lists m<n. But what
are they? We have no idea.
[3] Why not?
[4] When you say "I am missing several hundred errors", this could
mean that you want people to join in a deliberate campaign to destroy
Herbert Schildt's reputation (which is civilly and possibly criminally
liable) or that you somehow have determined that there are M~~1000
errors, but you present N=20. But in this context, N is not "many".\
[5] This is a very disturbing statement, as above. Did you lose them?
Did you forget them? Were you off medication? Were you on medication?
Or did you seek to form a cybernetic mob and gang up on Herb Schildt?
[6] Very disturbing.
[5] Followed by 20 errors
1. Negative numbers not ALWAYS represented in twos complement
notation: but this is what the head of department said in my graduate
level class on computer architecture, that IN GENERAL twos complement
is used.
2. Static global variables: the important distinction in computer
science is between variables which are static and have global scope,
and variables which are allocated either at procedure startup or in
blocks depending on the language, and have local scope. It is more
important to learn this in general for all programming languages so
that one can learn new languages.
3. Printing sizeof values as floats or doubles: although I do not
know why Herb did this, he did know, as you seem not to, that all ints
are floats and all floats are doubles in well-structured languages.
Because at the time C was almost as diverse of the languages of China,
Herb used the educated programmer's maxim, which is to first code as
if the compiler writers and language designers knew what he knows, and
fix problems later.
4. The put_rec code was errata. McGraw Hill offered you the chance to
work collegially with Herb to fix errata. Because his books were
successful, he's gone to several editions, and has fixed most of the
errata.
5. In college lectures which YOU DID NOT ATTEND, "binary operators"
often is verbal shorthand for "the commonly known binary arithmetic
operators, with logic operators being treated separately".
6. Wow, a reference to undefined behavior, of the same sort you make
in queue.c after two months work, and again, errata.
7. You really lay an egg. Like a disruptive student, you forbid the
teacher to talk about stacks as if it's even possible to implement C,
or any language, without stacks. You then surpass this, and say "the
'heap' is a DOS term".
8. Free as in speech, not beer. The storage was free. A minor
solecism at worst.
9. Mr. Snoid is lost in the void. Herb knows very well that to return
"void" is to return nothing and not return anything. You're disrupting
the class to show off. But worse, you're actually trying to destroy
someone so that you can get recognition you don't deserve.
10. C was not standardized at the time this book was written.
11. Shibboleth. And here, you're critiquing writing as a technical
editor when you gave evidence in the prologue that YOU CANNOT WRITE
with coherence or consistency.
12. Genuine errata, but don't break your arm patting yourself on the
back.
13. But, the operation fails if the file does not exist on the disk.
You're showing off. Sit down and shut the **** up. No wonder you
didn't take CS. Your presence would add nothing to the class.
14. Genuine errata. You know, you're not doing so good. Only 2/14 at
this point.
15. "But nor is it required"? A completely illiterate grammatical
solecism. How dare you pretend to be his tech editor? You were offered
a job finding errors. You found a few. Which means you're a
pretentious dweeb.
And furthermore, C should reject all-caps: it would do so if it were a
truly consistent language. But it as a real language in practice it
allows them because of Microsoft's market power. Get used to it.
16. Probably Herb's most serious error, but of the sort which creeps
into most computer books, including yours as you admit.
17. Errata.
18. Errata.
19. Herb is giving practical advice, and you're disrupting the class.
20. The order of evaluation is indeed specified in the variant
behavior of C compilers. The problem is that the standards committee
allowed incompetents like you to pay their way in to pad their resume,
along with thugs from vendors who'd fired their developers, and so,
the serious problems with the adolescent pre and post increment
operators were never fixed and remain to this day.
OK, you identified only 5 errata of the sort that exist in all books
unless the publisher allows the authors to use a system to avoid
errata. And yet you say:
"There are dozens of others, and I'm sure there's an effective
drinking game lurking in this book."
In other words, you Open Source here an Open Season on Schildt based
on your malice. This is civilly actionable libel.
