On 11/5/2012 20:44, Ozkan Sezer wrote:
> 
> If older gcc (I guess 4.6 is common as the old gcc) is OK with it, then
> please go ahead.

When you put it that way, it suddenly hit me that the vfwsprintf will
not really work if the user set -std=c++11 without including any C++
headers first. Such as when the use include <stdio.h> directly.

Any suggestions? The guard macro is:

#if defined(__cplusplus) && (__cplusplus >= 201103L) &&
!defined(_GLIBCXX_HAVE_BROKEN_VSWPRINTF)

_GLIBCXX_HAVE_BROKEN_VSWPRINTF will be set (or not) only after including
some basic C++ headers.

Basically, I didn't want users to be caught surprised. Any changes would
be on the mingw-w64 side, since the gcc change was just removing
_GLIBCXX_HAVE_BROKEN_VSWPRINTF to allow to_string to be used.



Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to