If there's anything worse than a redneck ignoramus, it's one with
broadband and a working credit card. Look at definition number 7.
We already pointed that out -- but you seem not to understand how [....]
Who's "we"? You're alone, I'd wot.
on the dictionary argument I'm with Mr Seebach. I've now quoted three
dictionaries that disagree with you. You really don't seem to
understand how dictionaries work (or you're pretending not to because
you won't admit you're wrong).
No, you've quoted inferior dictionaries and don't understand alternate
meanings. Furthermore, in use, "clear" as applied to "text" implies
"true".
"This book is a clear introduction to astrophysics" means two things:
(1) This book is not misleading
(2) This book is easy to understand
Note, however, that (2) implies (1), because "understanding" is
knowing, and knowing is, once again justified true belief. The only
way of saying that a book is false in a way that is easy to understand
or grok is to say that "the book is clearly wrong", which is logically
independent of "the book is clear": in the former, "clearly" as an
adverb applies to the main verb and the whole sentence, and it
ascribes the clarity to itself, never to "the book".
The EARLY Wittgenstein did say that anything that can be said can be
said clearly whether true or false. But what he meant was "in my
calculus", in his equivalent of a formal programming language. Herb
was writing in a natural language which for a mature Wittgenstein a
"form of life" in which there is, I believe, a fundamental asymmettry
between the true and the false such that false is never clear, because
in civil conversation we always exercise a tolerance, without which
conversation cannot take place.
In this form of tolerance, we always try to find the truth in what the
other says.
Now this sounds not to apply at all to programming for the simple
reason that autistic twerps are attracted to the apparent decidability
and lack of ambiguity of programming as a retreat from a messy world:
but the "structured walkthrough" discovery of old and the "extreme
pair programming" discovery of recent years means is that even in
programming we much love one another or die, or create buggy
software...while bragging how we don't...in jobs where the person
bragging that he doesn't, no longer creates code, but finds "issues"
to send to the "real" experts.
Constant fault finding by half-educated managers, employment-at-will,
and jobs as "consultants" which are just glorified temp jobs create
Fascistic levels of hatred for other people which emerge in Vitriolic
Tirades, fueled by envy at Herb's apparent financial success. I mean,
even my own small quarterly royalty check from Apress is pretty nifty
for it's money for which I don't have to work now which I didn't spend
in getting to work, or in buying tools for work, or in buying
overpriced food in restaurants. Given Herb's sales he may not have to
work, and this, I think, drives his enemies batshit.
If both Knuth and Dijkstra are right, and "programming" is
"communicating intentions clearly to another human about how you plan
to use a computer", then it was Seebach's responsibility, at which he
failed miserably, to discern the forest for the trees, and Herb's
intentions. In talking about a stack growing towards a heap in high
memory, Herb's intention was to show a concrete example of the two
fundamental runtime data structures in an instantiated way that the
student could play with until he understood why some things must be
malloc'd. He did so.
[...] a dictionary works. That gives you that one of many meanings has a
particular word, one of the many meanings of which is the meaning
you were asserting.
The Compact OED highlights the important meanings, whereas this rube
was overwhelmed by the full OED:
the thunder of desparate back-pedalling. You claimed my dictionaries
were bad because they weren't the OED. Now when someone quotes the OED
*that's* wrong as well. I've quoted the Shorter Oxford English
Dictionary is that as good as the Compact OED or not?
<check Amazon>
You Are An Idiot. The Compact OED has the *same text* as the full OED!
presumably you consider the important bits are the highlighted bits.
So do tell, which bits were highlighted under the entry for "clarity"?
<snip snip>