This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 15 May 2015 20:20:10 +0000
- Subject: [Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope
- Auto-submitted: auto-generated
- References: <bug-66157-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I already said that it works fine with C++ code *you* write, in any standard
mode. But don't expect everyone else's C++ code (including standard library
headers) to follow the old pre-1998 rules.
If you use -fno-for-scope you are no longer compiling standard C++, you are
compiling some non-standard dialect. That has always been true, it's not new
for C++11.