[PATCH] New functions wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf
Jeff Johnston
jjohnstn@redhat.com
Thu Mar 5 21:57:00 GMT 2009
- Previous message (by thread): [PATCH] New functions wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf
- Next message (by thread): [PATCH] New functions wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Corinna Vinschen wrote:
> On Mar 5 14:40, Howland Craig D (Craig) wrote:
>
>> Since the wide-character functions were introduced for C99, which also
>> introduced and requires the long long (and long double) types, does it
>> make sense to propagate the printf _WANT_IO_LONG_LONG configuration
>> option to the wide functions?
>>
>
> IMHO, yes. There might still a legitimate interest to keep this in for
> a couple of smaller targets.
>
>
Agreed.
>> Should the Newlib printf flag extensions (DOUq) be kept for wprintf?
>>
>
> Probably not. I thought to remove them as well at one point, but
> wanted to discuss this on the list first. I just forgot to mention this
> in my patch submission. Thanks for following up with this question.
> I thin we should remove them, yes. I'm interested in Jeff's opinion,
> though.
>
>
DOU can/should be removed. q is a gnu c compiler extension so we should
consider keeping it at least optionally. It is in the glibc
documentation for formatted output.
-- Jeff J.
- Previous message (by thread): [PATCH] New functions wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf
- Next message (by thread): [PATCH] New functions wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Newlib
mailing list