Re: inconsistency in libintl_vsnprintf interface under Windows

[Ben Pfaff]

Bruno Haible <address@hidden> writes:

> Ben Pfaff wrote:
>> [...regarding libintl_[v]snprintf...]
>> I propose to fix it by always using the C99 semantics.
>
> This is outside of the scope of libintl. libintl cares about the needs of
> internationalization. The right place for such C99 or POSIX compliance fixes
> is gnulib.

OK.  I'm happy to do that.  It's just that libintl interferes
with the usual gnulib approach, because libintl.h contains:
    #undef snprintf
    #define snprintf libintl_snprintf
This overrides the #define for snprintf that gnulib (or at least
the module I'm working on) puts in <config.h>.  I guess that one
option would be to also "#define libintl_snprintf rpl_snprintf",
but that seems silly to me.  Is that the approach you'd suggest?
If not, do you have any other suggestion?
-- 
"Implementation details are beyond the scope of the Java virtual
 machine specification.  One should not assume that every virtual
 machine implementation contains a giant squid."
--"Mr. Bunny's Big Cup o' Java"