Stephan Bergmann wrote: > Right, forgot about the Clang case. So that would mean keeping > SAL_THROW non-deprecated, making it a nop with Clang > --disable-dbgutil (but making it a non-nop for GCC generally), and > changing the cppumaker-generated headers to use SAL_THROW. > So the change meanwhile got committed as 0295bd6b3f21dd648af6145ca23d90467f3cec73, and while discussion was ongoing here & on irc, I went the "bin exception specs entirely" route for c++.
I concede there's potential debugging utility in having compilers generate runtime checks for exception specs in dbg_util mode, I wonder though if this is worth the mess we'd generate. With SAL_THROW & exception specs on api headers removed, there's a very nice & substantial cleanup task possible subsequently, that removes it from all implementation methods, too. Cheers, -- Thorsten
pgpkq3oMnCgY0.pgp
Description: PGP signature
_______________________________________________ LibreOffice mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice
