Follow-up Comment #14, bug #40361 (project make):
I would be surprised if it's va_copy(). On the other hand I'm surprised that
a UNIX variant in 2013 doesn't comply with a C standard which is 14+ years old
now... I sort of expect that from Windows as they've all but abandoned C, but
not a UNIX system.
On the other hand we do try to meet C89 compliance (at least for the standard
library and language). There are two alternative non-standard semantics of
vsnprintf() that I'm aware of: one where it returns <0 if the buffer is too
small (Windows does it this way) and the other where it returns the number of
bytes written and doesn't write the last nul byte (like strncpy).
We may need to switch to gnulib functions or else avoid the *nprintf()
variants. I'll look into this.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?40361>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
