[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope

2015-05-18 Thread luca.stoppa at bbh dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157 --- Comment #9 from Luca Stoppa --- I see. Thanks again for your answer.

[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope

2015-05-15 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157 --- Comment #8 from Jonathan Wakely --- 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 us

[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope

2015-05-15 Thread luca.stoppa at bbh dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157 --- Comment #7 from Luca Stoppa --- Well, even if my production code is 20 years old, the example I have attached isn't. It is valid c++11/14 code. Would you call something like this "old c++ code"? #include int main() { std::vector v{1,2,

[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope

2015-05-15 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157 Andreas Schwab changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope

2015-05-15 Thread luca.stoppa at bbh dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157 --- Comment #5 from Luca Stoppa --- I think you can close this "bug".

[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope

2015-05-15 Thread luca.stoppa at bbh dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157 --- Comment #4 from Luca Stoppa --- It is a very very very... old application written like 20 years ago. Anyway, we'll try to remove that option from our build process. Thanks for your answer.

[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope

2015-05-15 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157 --- Comment #3 from Jonathan Wakely --- The option works exactly as documented, and can be used freely with your own code if you need to compile old code. Obviously if you include any code you didn't write (such as standard library headers) then

[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope

2015-05-15 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157 Jonathan Wakely changed: What|Removed |Added Severity|major |minor --- Comment #1 from Jonathan Wak

[Bug libstdc++/66157] bits/random.tcc compiler error when using -fno-for-scope

2015-05-15 Thread luca.stoppa at bbh dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66157 --- Comment #2 from Luca Stoppa --- I'm sorry, what do you mean with "don't do that"? Can you please tell me whether c++11/14 with -fno-for-scope is supported?