How printf() works???????

[Richard]

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

santosh <santosh.k83@gm ail.comwrites:

Robbie Hatley wrote:
>

>>
>"santosh" <santosh.k83@gm ail.comwrote:
>>

>>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.

>>
>OOOPS!!! So *THAT'S* what you meant!

>
That's what Richard Riley meant when he said "It won't actually."
up-thread.

Do you think? :-;

[Kenny McCormack]

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

In article <fqrdd4$tll$2@r egistered.motza rella.org>,
Richard <devr_@gmail.co mwrote:

>santosh <santosh.k83@gm ail.comwrites:
>

>Robbie Hatley wrote:
>>

>>>
>>"santosh" <santosh.k83@gm ail.comwrote:
>>>
>>>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.
>>>
>>OOOPS!!! So *THAT'S* what you meant!

>>
>That's what Richard Riley meant when he said "It won't actually."
>up-thread.

>
>Do you think? :-;

Some folks are a little slow on the uptake.

But they do (sometimes) get it eventually.

[Richard]

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

santosh <santosh.k83@gm ail.comwrites:

Richard wrote:

>santosh <santosh.k83@gm ail.comwrites:

>>Robbie Hatley wrote:
>>>"Richard" <devr_@gmail.co mwrote:
>>>>Richard Heathfield <rjh@see.sig.in validwrites:

>
<snip>
>

>>>x < 30 is a relational expression, and all expressions have
>>>values. Relational expressions have the value 0 if they're false,
>>>and 1 if they're true. So x < 30 will evaluate to 0 if x is less
>>>than 30, and 1 otherwise.
>>>>>
>>>>It won't actually.
>>>>
>>>How do you figure? It does in standard C. If it doesn't for you,
>>>then your compiler is broken and you should get a better one.
>>>
>>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. There is
>no evil intent in my correction. Why you feel the need to confirm his
>"mistake" is very strange.

>
Because he did not spot RJH's error and therefore, could not understand
your correction.

So therefore, maybe he should post nothing? Did that cross your mind? he
waffled on about my broken compiler and its as clear as day he never
tried the code with his wonderful,all singing, all dancing compiler.

>

>Possibly you should inform Robbie to be
>less quick to tell people their compilers are broken and that they
>should get a new one?

>
He misread RJH's erroneous sentence. Why blame him for it?

You've gone to the dark side Santosh. I "blame" him for nothing. I am
merely pointing out that one should know what one is talking about before
slamming other posters and insulting their compiler ..... In this case
he didn't bother to, or was unable to, verify my statement. Regardless
of that he started on about standard C and my compiler being broken. I
didn't even need to compile anything to see the obvious mistake that
Heathfield made. See other post for reasons not to harp on about what
that mistake was - it was abundantly clear to any C programmer. Yes it
was a "mistake" but one worth pointing out as RH had gone to great
lengths to explain the boolean nature of the expression only to get it
180% wrong : a slip of course. I don't honestly believe that RH thinks
that 1<30 returns 0 for example. hence there was no malevolence, no
crowing in my reply. Merely "incorrect" or there abouts. Your need to
jump to RHs defence surprises me. There is no need.

[santosh]

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

Richard wrote:

santosh <santosh.k83@gm ail.comwrites:
>

>Richard wrote:

>>santosh <santosh.k83@gm ail.comwrites:
>>>Robbie Hatley wrote:
>>>>"Richard" <devr_@gmail.co mwrote:
>>>>>Richard Heathfield <rjh@see.sig.in validwrites:

>>
><snip>
>>

>>>>x < 30 is a relational expression, and all expressions have
>>>>values. Relational expressions have the value 0 if they're
>>>>false, and 1 if they're true. So x < 30 will evaluate to 0 if x
>>>>is less than 30, and 1 otherwise.
>>>>>>
>>>>>It won't actually.
>>>>>
>>>>How do you figure? It does in standard C. If it doesn't for you,
>>>>then your compiler is broken and you should get a better one.
>>>>
>>>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. There
>>is no evil intent in my correction. Why you feel the need to confirm
>>his "mistake" is very strange.

>>
>Because he did not spot RJH's error and therefore, could not
>understand your correction.

>
So therefore, maybe he should post nothing? Did that cross your mind?

He misread RJH's statement and that is what I brought to his notice.
What he said to you about your compiler is beside the point and did not
strike me as being important enough to comment on.

he waffled on about my broken compiler and its as clear as day he
never tried the code with his wonderful,all singing, all dancing
compiler.

OP's code was not relevant to spotting RJH's mistake. Compiling OP's
code (which would require some completion to make it compilable) would
do nothing towards spotting (or not spotting) RJH's typo.

So in this case debating about his compiler and your compiler are
irrelevant.

It's really simple:

1. RJH made a *genuine* mistake.
2. You made a *genuine* correction to his mistake.
3. Robbie Hatley misread RJH's statement so that he read what RJH had
meant to say, not what he wrote.
4. Therefore Robbie Hatley took your statement as correcting a (to him)
correct statement.
5. I pointed out to Robbie Hatley that he misunderstood your correction
because he had misread RJH's erroneous statement.
6. Robbie Hatley acknowledged his misreading and we thought everything
was done and dusted, but...
7. You have taken exception with my *well* *intentioned* correction of
Robbie Hatley's misunderstandin g, saying that I should have instead
flamed him for a comment that was essentially irrelevant and beside the
point, and one that was moreover, aimed at you.
8. You have also responded (at least) twice to RJH about this whole mess
including also a tedious recap of your well known opinions about this
group.
9. Surprisingly, you have not yet responded to Robbie Hatley, the poster
who has apparently offended you with his remarks about your compiler,
instead choosing to snipe at posters whose only intention was to clear
up the misunderstandin g that started this subthread and thus to get it
closed.

>>Possibly you should inform Robbie to be
>>less quick to tell people their compilers are broken and that they
>>should get a new one?

>>
>He misread RJH's erroneous sentence. Why blame him for it?

>
You've gone to the dark side Santosh.

Mind explaining what you mean by this?

I "blame" him for nothing. I am
merely pointing out that one should know what one is talking about
before slamming other posters and insulting their compiler ..... In
this case he didn't bother to, or was unable to, verify my statement.

He (Robbie Hatley) did not bother to verify your statement for the
simple fact that he thought you were obviously wrong, since you were
apparently refuting a 100% correct statement by RJH. He missed the fact
that he had misread RJH mistake.

This sometimes happens. It's unfortunate and the whole subthread could
have closed down with my reply to Robbie Hatley and his response to me,
but now we are having a vigorous mud-slinging contest going on.

Regardless of that he started on about standard C and my compiler
being broken. I didn't even need to compile anything to see the
obvious mistake that Heathfield made. See other post for reasons not
to harp on about what that mistake was - it was abundantly clear to
any C programmer.

Yes, but Robbie Hatley misread it. Which is what I pointed out to him,
carefully ignoring his other statement about your compiler since that
was not relevant, either to me or to this subthread.

Yes it was a "mistake" but one worth pointing out as
RH had gone to great lengths to explain the boolean nature of the
expression only to get it 180% wrong : a slip of course. I don't
honestly believe that RH thinks that 1<30 returns 0 for example. hence
there was no malevolence, no crowing in my reply. Merely "incorrect"
or there abouts.

Where did I imply that there was malevolence or crowing in your reply?

Your need to jump to RHs defence surprises me. There is no need.

*sigh* Once more:

I did _not_ jump to RJH's defence. I jumped in to correct Robbie
Hatley's mistake. Can you make out the difference, or are you far too
biased against RJH that you see a correction to a post aimed at a post
that was a correction to a post by RJH, as a defence of RJH?

[Antoninus Twink]

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

On 7 Mar 2008 at 14:25, Richard wrote:

Your need to jump to RHs defence surprises me. There is no need.

It doesn't surprise me. Santosh's only function in this group is to
groom the fleas of Heathfield the alpha male.

[Richard]

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

Antoninus Twink <nospam@nospam. invalidwrites:

On 7 Mar 2008 at 14:25, Richard wrote:

>Your need to jump to RHs defence surprises me. There is no need.

>
It doesn't surprise me. Santosh's only function in this group is to
groom the fleas of Heathfield the alpha male.

That's as may be, but he seems to have got a bit wrapped in this one for
some reason. And the bottom line of this thread is abundantly clear to
anyone who read as far as RHs polite reply where he pretty much agreed
with each and every point I had made.

[Antoninus Twink]

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

On 7 Mar 2008 at 13:44, Richard Heathfield wrote:

Richard said:

>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.

Wow, CBF has really been cut loose. Clique status lost and no mistake.

<typical Heathfield cant and hypocrisy snipped>

[Richard]

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

Antoninus Twink <nospam@nospam. invalidwrites:

On 7 Mar 2008 at 13:44, Richard Heathfield wrote:

>Richard said:

>>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.

>
Wow, CBF has really been cut loose. Clique status lost and no mistake.
>
<typical Heathfield cant and hypocrisy snipped>

I always felt he was treated more like the grumpy old
farm dog. Ultimately useless, but nice to pet occasionally.

[Richard]

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

lawrence.jones@ siemens.com writes:

Richard <devr_@gmail.co mwrote:

>santosh <santosh.k83@gm ail.comwrites:
>>

>>Richard wrote:
>>>santosh <santosh.k83@gm ail.comwrites:
>>>>Robbie Hatley wrote:
>>>>>"Richard " <devr_@gmail.co mwrote:
>>>>>>Richard Heathfield <rjh@see.sig.in validwrites:
>>>
>><snip>
>>>
>>>>>x < 30 is a relational expression, and all expressions have
>>>>>values. Relational expressions have the value 0 if they're false,
>>>>>and 1 if they're true. So x < 30 will evaluate to 0 if x is less
>>>>>than 30, and 1 otherwise.
>>>>>>>
>>>>>>It won't actually.
>>>>>>
>>>>>How do you figure? It does in standard C. If it doesn't for you,
>>>>>then your compiler is broken and you should get a better one.
>>>>>
>>>>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. There is
>>>no evil intent in my correction. Why you feel the need to confirm his
>>>"mistake" is very strange.
>>>
>>Because he did not spot RJH's error and therefore, could not understand
>>your correction.

>>
>So therefore, maybe he should post nothing? Did that cross your mind? he
>waffled on about my broken compiler and its as clear as day he never
>tried the code with his wonderful,all singing, all dancing compiler.

>
That's the risk you take when you post such a terse answer -- people
don't know whether you're confused or just being coy. Expanding your
answer just a tad, say to something like:
>
It won't actually, it's the other way around.
>
would have saved a whole flurry of messages and some hard feelings.

Not really. Santosh and the others got it. I explained in another post
why I didn't do that. But point taken, even though I don't necessarily agree.

[Antoninus Twink]

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

On 7 Mar 2008 at 17:15, Richard wrote:

Antoninus Twink <nospam@nospam. invalidwrites:
>

>On 7 Mar 2008 at 13:44, Richard Heathfield wrote:

>>Richard said:
>>>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.

>>
>Wow, CBF has really been cut loose. Clique status lost and no mistake.
>>
><typical Heathfield cant and hypocrisy snipped>

>
I always felt he was treated more like the grumpy old
farm dog. Ultimately useless, but nice to pet occasionally.

Either way, he's definitely off to the glue factory now.

[santosh]

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

Richard wrote:

<snip>

Santosh, you're rapidly becoming a bore in your attempts to make your
bones. Heathfield is big enough and ugly enough to take care of
himself. As, I am sure, is Robbie.
>
I'm not reading any more of your word games. Enough.

Thanks for sending a SIGSTOP to yourself. For a moment there I feared
that I would be stuck spinning in an endless loop, explaining the same
things to you over and over.

[Kenny McCormack]

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

In article <fqrjj3$sc8$1@r egistered.motza rella.org>,
Richard <devr_@gmail.co mwrote:
....

>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.

Not only a waste of disk space, but a waste of space, period.
And of air.

[Kenny McCormack]

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

In article <fqrnq2$iut$1@r egistered.motza rella.org>,
Richard <devr_@gmail.co mwrote:
....

>What is it with you and apologising for other peoples mistakes?

Good point. I refer you to:

http://redwing.hutman.net/~mreed/warriorshtm/sycophant.htm

[CBFalconer]

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

santosh wrote:

Richard wrote:
>

.... snip ...

>

>Your need to jump to RHs defence surprises me. There is no need.

>
*sigh* Once more:
>
I did _not_ jump to RJH's defence. I jumped in to correct Robbie
Hatley's mistake. Can you make out the difference, or are you far
too biased against RJH that you see a correction to a post aimed
at a post that was a correction to a post by RJH, as a defence of
RJH?

You do realize that that Richard is a known troll? Why feed it?

--
[mail]: Chuck F (cbfalconer at maineline dot net)
[page]: <http://cbfalconer.home .att.net>
Try the download section.



--
Posted via a free Usenet account from http://www.teranews.com

[Richard]

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

CBFalconer <cbfalconer@yah oo.comwrites:

santosh wrote:

>Richard wrote:
>>

... snip ...

>>

>>Your need to jump to RHs defence surprises me. There is no need.

>>
>*sigh* Once more:
>>
>I did _not_ jump to RJH's defence. I jumped in to correct Robbie
>Hatley's mistake. Can you make out the difference, or are you far
>too biased against RJH that you see a correction to a post aimed
>at a post that was a correction to a post by RJH, as a defence of
>RJH?

>
You do realize that that Richard is a known troll? Why feed it?
>
--
[mail]: Chuck F (cbfalconer at maineline dot net)
[page]: <http://cbfalconer.home .att.net>
Try the download section.

It is amusing how foolish you are. I would put my credentials against
yours any day. But that would be "real world". In clc, you are king pin
Chuck. Enjoy!