From: "Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
Organization: Darmstadt University of Technology
To: djgpp-workers AT delorie DOT com
Date: Wed, 4 Sep 2002 12:06:57 +0100
Subject: conversion specifiers and _doprnt
X-mailer: Pegasus Mail for Windows (v2.54DE)
Message-ID: <AB6DAB53745@HRZ1.hrz.tu-darmstadt.de>
X-MailScanner: Found to be clean
Reply-To: djgpp-workers AT delorie DOT com

I have almost finished the implementation of the numbered conversion specifier (aka %n$.m$)
to _doprnt. While inspecting the sources and comparing the djgpp implemented conversion
specifiers with the standard (IEEE Std 1003.1-2001, at www.opengroup.org) I have found the
following issues I can not understand:

   Implemented/Not implemented in djgpp:                          Standard:
1: D (uppercase d) Signed long integer. Implemented               Not defined.
   If I use %D in printf, gcc complains with:
     unknown conversion type character 'D' in format.

2: F (uppercase f) Not implemented                                Defined.

3: O (uppercase o) unsigned long integer (octal). Implemented     Not defined.
   If I use %O in printf, gcc complains with:
     unknown conversion type character 'O' in format.

4: U (uppercase u) unsigned long integer. Implemented             Not defined.
   If I use %U in printf, gcc complains with:
     unknown conversion type character 'U' in format.

The D und U specifiers are also mentioned in the libc docs.
Am I missing somthing here? Should these specifiers be removed (D,O,U)/added (F)?

Regards,
Guerrero, Juan Manuel