Hello John and Ruben! On Sun, Apr 7, 2013 at 3:04 PM, John E. / TDM <[email protected]> wrote: > On 4/7/2013 12:44 PM, Ruben Van Boxem wrote: > > 2013/4/7 K. Frank <[email protected]> > >> Or maybe "-std=gnu++11" would be better still. The best of both >> worlds! > > No. Don't use that. That's the road to non-portability. Dark things live > there. > > Actually, when no -std option is specified GCC uses gnu++98 as its default > (as opposed to c++98) -- see > <http://gcc.gnu.org/onlinedocs/gcc/Standards.html>. So when the GCC vanilla > default *is* changed, it will most likely become gnu++11. > > As for the standard option. No sorry, ain't gonna happen. It's not 100% > backwards compatible and will most likely even break the GCC build itself > (mostly due to narrowing conversions in braced-init-lists (this is a > guess)). > > However, I agree that it's probably not the right time yet to start using > C++11 by default.
Aw, come on. No guts, no glory! Besides, I was only suggesting making -std=gnu++11 the default for Ruben's fringe, out-there, std::thread-enabled build that people will only want to use if the use std::thread, which will anyway require them to use -std=gnu++11 (or -std=c++11). > -John E. / TDM Best. K. Frank ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
