> From: Bruno Haible <[email protected]> > Cc: [email protected], [email protected], [email protected] > Date: Thu, 06 Nov 2025 12:33:40 +0100 > > Eli Zaretskii wrote: > > > And Gnulib's vasprintf is huge, basically performing > > all the formatting by itself. > > Yes, but this is not the function that is meant to be invoked here. > stdio-consolesafe.c is meant to invoke mingw's vasprintf() function. > > > Btw, stdio-consolesafe.c uses vasprintf, which mingw.org's MinGW > > doesn't have. > > Gnulib does not support the old mingw.org mingw any more. The > mingw.org website is dead, and the development has been taken > over by the mingw-w64 project more than 15 years ago [1].
I know. But I still use it, and it is the only development environment capable of building Emacs that will run on versions of Windows before Windows 7, which MinGW64 dropped, and Emacs still wants to support. > The code in stdio-consolesafe.c is conditionalized with > __USE_MINGW_ANSI_STDIO. mingw.org's MinGW defines that by default for a long time. > Does your old mingw have the functions __mingw_[v][f]printf? Yes. > Do these functions in your old mingw output double-byte characters > one byte at a time? I believe so, because they use fputc to output characters (bytes) one by one. > Does your old mingw enable these functions under a different > condition than __USE_MINGW_ANSI_STDIO? They can _also_ be enabled under a different condition, yes. But I don't see how this is relevant. > Does your old mingw have the vasprintf() function? No, it doesn't.
