Re: viewing mbr os descriptor

[CBFalconer]

Jens Thoms Toerring wrote:

Bill Cunningham <nospam@nspam.c omwrote:
>

.... snip ...

>

>This just makes printf more complicated for me. I read the page.
>I don't know if I need a length conversion or a format specifer.

>
Sorry, but using printf() correctly is a bit complicated.
Moreover printf() is a function were, if you screw up, there
is nothing the compiler or anything else can help you with.
That's a common problem of so-called variadic functions in
C (all those that accept an unspecified number of arguments,
i.e. have three dots '...' in the prototype). These functions
have to rely on that the format specifiers and the actual
arguments match (or at least deviate not too much). E.g.
if you do

This is not on-topic in comp.programmin g. It belongs on
comp.lang.c, to which I have rerouted it and set follow-ups.

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


** Posted from http://www.teranews.com **

[Keith Thompson]

Re: viewing mbr os descriptor

CBFalconer <cbfalconer@yah oo.comwrites:

Jens Thoms Toerring wrote:

>Bill Cunningham <nospam@nspam.c omwrote:
>>

... snip ...

>>

>>This just makes printf more complicated for me. I read the page.
>>I don't know if I need a length conversion or a format specifer.

>>
>Sorry, but using printf() correctly is a bit complicated.
>Moreover printf() is a function were, if you screw up, there
>is nothing the compiler or anything else can help you with.
>That's a common problem of so-called variadic functions in
>C (all those that accept an unspecified number of arguments,
>i.e. have three dots '...' in the prototype). These functions
>have to rely on that the format specifiers and the actual
>arguments match (or at least deviate not too much). E.g.
>if you do

>
This is not on-topic in comp.programmin g. It belongs on
comp.lang.c, to which I have rerouted it and set follow-ups.

And you've snipped much of the previous article, which makes it
difficult for those of us who saw your followup in comp.lang.c but not
the previous article in comp.programmin g to respond intelligently.

--
Keith Thompson (The_Other_Keit h) kst-u@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Bill Cunningham]

Re: viewing mbr os descriptor


"Keith Thompson" <kst-u@mib.orgwrote in message
news:lnhccvdrnn .fsf@nuthaus.mi b.org...

>>Sorry, but using printf() correctly is a bit complicated.

Ok. I guess it's time to learn.

>>Moreover printf() is a function were, if you screw up, there
>>is nothing the compiler or anything else can help you with.
>>That's a common problem of so-called variadic functions in
>>C (all those that accept an unspecified number of arguments,
>>i.e. have three dots '...' in the prototype). These functions
>>have to rely on that the format specifiers and the actual
>>arguments match (or at least deviate not too much). E.g.
>>if you do

>>
>This is not on-topic in comp.programmin g. It belongs on
>comp.lang.c, to which I have rerouted it and set follow-ups.

>
And you've snipped much of the previous article, which makes it
difficult for those of us who saw your followup in comp.lang.c but not
the previous article in comp.programmin g to respond intelligently.
>

Now I guess there are #$][ and maybe even more specifers with printf.
I've never seen this in a tutorial. All I know are % and a format specifier
or maybe a whole number or decimal with fraction such as 2.2 between the
format specifier and conversion type. For example %2.2f

Bill