Re: How printf() works???????

Richard Heathfield <rjh@xxxxxxxxxxxxxxx> writes:

[Well, what an eye-opener. On the basis of his previous, helpful, reply, I
unplonked "Just Richard" on a whim, and look what I found...]

Richard said:

santosh writes:

<snip>

The expression x < 30 will evaluate to 1 if x is less than 30 and zero
otherwise. Richard said the reverse, by mistake I'm sure.

Getting something totally backwards is,of course, a mistake.

Yes.

There is no evil intent in my correction.

Believe it or not, I believe you. It was an honest correction to an honest
mistake.

Yes.


Why you feel the need to confirm his
"mistake" is very strange. Possibly you should inform Robbie to be less
quick to tell people their compilers are broken and that they should get
a new one?

And here you make a very reasonable point. It's better not to be
hostile

I am a reasonable person. To be called "unreasonable" by some of the clc
regs here, confirms that to me.

(not something I always manage), but if you're determined to be hostile,
you'd better be very, very sure that you're right! It's a lot costlier
(blushes, etc) to apologise for an incorrect correction if that
"correction" was aggressive. (I am well aware of this from personal
experience, alas.)

We all make mistakes. To err is human.


Which leads to the question "Why didn't you explain why Heathfield was
wrong". And the answer is simple : I don't believe in treating people
like idiots. Let them look and think the problem over themselves. They
can always come back and say "you have me stumped", what is the issue?".

I kind of agree with this. When someone who I *know* ought to know better
misinterprets a statement and issues a misguided rejoinder (and if there
are no other responses in the feed that have caught the misguidedness), I
will generally say something like "how sure are you about that?" or "read
it again, <name>", or whatever. If it's someone I don't recognise, or whom
I think is unlikely to spot on re-reading the reason that their
"correction" is wrong, I am more likely to give a detailed explanation.

A good C programmer and "team player" thinks for themselves. RH had said
enough about the comparison expression for anyone with half a clue to
see why he had made a mistake in his final analysis.

Yes. In fact, this was particularly unfortunate, because I was rather
pleased with my answer - not because it was difficult to write (it wasn't,
except for the getting-it-right part!), but because after posting it I
downloaded another bunch of articles, and all the other replies I saw
were, I felt, leaning (and in some cases positively *bending*) in the
direction of unfriendliness and unhelpfulness. I think that's a shame.

But of course, giving credence and credit to other posters is becoming a
rarer and rarer thing these days with posters like CBF riding in on
their chargers at a moments notice.

Again, I am struggling to disagree with you here, and failing.


Too many of the "clique" (and you are one) are too willing to be overly
forceful with your views IMO. Especially on topicality.

CBF, however, is just a waste of disk space IMO. He is wrong more often
than he is right. And he is downright rude and objectionable at his
best.


.

Relevant Pages

  • Re: How printf() works???????
    ... unplonked "Just Richard" on a whim, ... Getting something totally backwards is,of course, a mistake. ... It was an honest correction to an honest ... whole to relax its topicality restrictions somewhat. ...
    (comp.lang.c)
  • Re: How printf() works???????
    ... Relational expressions have the value 0 if they're false, ... Richard said the reverse, by mistake I'm sure. ... Getting something totally backwards is,of course, a mistake. ... a rarer and rarer thing these days with posters like CBF riding in on ...
    (comp.lang.c)
  • Re: How printf() works???????
    ... Richard said the reverse, by mistake I'm ... Getting something totally backwards is,of course, a mistake. ... What he said to you about your compiler is beside the ... Robbie came flying in telling me my ...
    (comp.lang.c)
  • Re: Code Review - is this code shit
    ... Richard "Buckwheat" Heathfield are falling all over yourselves to ... mistake, and you are falling all over yourself trying to avoid your ... made an incorrect "correction". ... The important issue is that of incorrectly "correcting" someone, ...
    (comp.lang.c)
  • Re: Chez Watt: Re: Manufacture vs. Artifact?
    ... Not true - I have voted for evolutionists who made amusingly ridiculous ... problem is that there are precious few nominations to choose from that are ... Again you claim this was a mistake by Richard. ...
    (talk.origins)