Le 05/07/2016 12:11, Jean-Marc Lasgouttes a écrit :
Le 04/07/2016 à 23:34, Guillaume Munch a écrit :
Le 04/07/2016 12:25, Jean-Marc Lasgouttes a écrit :
commit 67ac031a33b1621fdadb903422de598595cc08d2
Also, use gnu++11 unconditionnally with gcc as we used to do
before 67385e69.
Does this mean more problems that go unnoticed until people on OSX or
Windows try to compile?
No, because we use clang too :)
What do you mean? I would have to use clang if I want to compile without
gnu extensions?
I figured that the difference were minimal, but if I am wrong I can
revert this part of course. Only cygwin requires gnu++11.
As far as I understand, the difference is precisely to enable
non-standard extensions. I do see the point of disabling non-standard
extensions for a cross-platform software.
