[Mingw-notify] [ mingw-Bugs-2797669 ] -std=c++0x is error, but -std=gnu++0x is OK!

[SourceForge.net <no...@so...>]

Bugs item #2797669, was opened at 2009-05-28 00:43
Message generated for change (Settings changed) made by keithmarshall
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=2797669&group_id=2435

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mingw runtime
Group: None
Status: Open
Resolution: None
Priority: 9
Private: No
Submitted By: Loaden YC (loadeng)
>Assigned to: Danny Smith (dannysmith)
Summary: -std=c++0x is error, but -std=gnu++0x is OK!

Initial Comment:
if use -std=c++0x, will error:

d:\ycdeng\qpdev\bin\..\lib\gcc\mingw32\4.4.1\include\c++\cwchar|159|error:
'::swprintf' has not been declared|
d:\ycdeng\qpdev\bin\..\lib\gcc\mingw32\4.4.1\include\c++\cwchar|166|error:
'::vswprintf' has not been declared|
||=== Build finished: 2 errors, 0 warnings ===|

if want fix, need #undef __STRICT_ANSI__, see: stdio.h
or option is: -U__STRICT_ANSI__

but when change to: -std=gnu++0x, it's OK!


----------------------------------------------------------------------

>Comment By: Keith Marshall (keithmarshall)
Date: 2010-02-04 17:14

Message:
This duplicates bug #2373234
https://sourceforge.net/tracker/?func=detail&aid=2373234&group_id=2435&atid=102435

Since, as I've noted on that ticket, it was Danny's patch which introduced
the inconsistency, I'm referring this to him.

----------------------------------------------------------------------

Comment By: Aaron W. LaFramboise (aaronwl)
Date: 2009-06-24 05:19

Message:
Confirmed.  This bug exists in 4.4.0 too.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=2797669&group_id=2435