On 02/23/2012 05:08 PM, Lubos Lunak wrote:
commit 437fe5a444411f68d1848c49121394f16f09611b made me notice that we
actually build with -std=c++0x and not -std=gnu++0x, which I think would make
more sense and be consistent with the case when we do not build in C++0x
mode.
If you look at the gcc manpage for the description of -std, you'll notice
that the C++ default is gnu++98, and c++98 is switched to also by
using -ansi. So if we default to c++0x, we pretty much default to the more
strict -ansi, only in C++0x mode. That should mean that gcc is more strict
than its default and e.g. some of its extensions are disabled.
Argh, yes, failed to note that when I prepared the patch linked above.
Any objections to switching to gnu++0x ?
Sounds good.
Stephan
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.