On Thursday 29 of November 2012, Michael Stahl wrote:
also iirc LLVM/clang has no option similar to -fno-enfore-eh-specs, i.e.
it always enforces exception specifications, so if we were to use that
for product builds (no i am not proposing that :) ), we'd need to not
generate the throw in cppumaker or use some macro to nerf it...
AFAIK Clang is now the official compiler for MacOSX and *BSD, so I guess
sooner or later there will be product builds built with it.
That said, if it really makes a difference, I haven't look at the source, but
I expect implementing -fno-enforce-eh-specs in Clang should be no big deal.
--
Lubos Lunak
l.lunak@suse.cz
Context
Re: [API] Some more cleanup ideas · Lubos Lunak
Re: [API] Some more cleanup ideas · Stephan Bergmann
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.