Re: [Mingw-users] using snprintf og gnulib

[Keith M. <kei...@us...>]

On Wednesday 29 August 2007 14:51, Brian Dessent wrote:
> > my question is not how I import or compile a gnulib module. I have
> > a valid libgnu.a file, valid object files. When I look at the
> > compilation and link commands of my lib, I don't see anything
> > different from the command I use for my test program.
>
> Because the m4 macros add a "#define snprintf rpl_snprintf" to
> config.h if they detect that the platform's version is not C99
> compliant in order to select the gnulib replacement, but that's not
> happening in your case for whatever reason.

Just a wild guess, (and I don't have time to investigate just now)...

Would the very latest runtime snapshot, which aliases snprintf to 
__mingw_sprintf, cause gnulib's m4 test to accept the platform snprintf 
as a C99 compliant implementation, and so not generate this #define?

AIUI, the rationale for that update was to improve C99 conformance, 
which it does in many respects, but apparently it doesn't include `%a' 
format conversion (yet).  To what extent does gnulib verify the C99 
conformance?  Are there options to check for specific aspects of 
conformance, (such as specifically for `%a' format conversion)?

Regards,
Keith.