Mail Archives: djgpp/2004/12/19/11:16:57
Since you are up on this, PLEASE explain why the
%U and %D mentioned in libc.txt (or libc.info)
when it is actually flagged as a non-existing entity...
What is/was the purpose of %D, %U ?
What I did was to attempt to convert those *.info
files into a more useful *.txt files (that was done long ago),
ALL material is in there, but apparently there are also high-bit
characters present as well and my eye is over-trained to ignore
areas of "garbage", which is why I missed what I needed.
'h', 'l', etc., are indeed mentioned!
On 19 Dec 2004 00:11:29 GMT, Hans-Bernhard Broeker
<broeker AT physik DOT rwth-aachen DOT de> wrote:
>Radical NetSurfer <RadSurfer AT yahoo DOT com> wrote:
>
>[... much snipped ...]
>
>> What is this indicating?
>
>To put it bluntly: it indicates that you haven't read the fine manual
>on printf() with sufficient attention yet. Please do so immediately.
>
>> %ld works, but get this, according to 'libc.txt' which describes the
>> library functions (by category, etc.) and looking at
>> printf
>
>There is no 'libc.txt' that is supposed to document the details of
>DJGPP's implementation of printf(). The main documentation is libc.info.
>
>> there is *NO* sign of &h, no sign of 'l' as a long modifier,
>
>Huh? What's this, then (quoted straight from 'info libc alpha printf':
>
> * An optional conversion qualifier, which may be `h' to specify
> `short', `l' to specify long ints, or `L' to specify long doubles.
> Long long type can be specified by `L' or `ll'.
- Raw text -