On Tuesday 03 of April 2012, Noel Grandin wrote:
Don't we have a macro for marking these kinds of things as deprecated?
There is SAL_DEPRECATED, but that is for marking C++ code, it doesn't work
during preprocessing.
is there some macro that is defined by LO build system for which we can
assume that nobody outside of LO uses it? we could wrap the deprecated
cruft in an #ifndef now, and remove it for LO4.
I could use a macro for a somewhat similar purpose, I'd need #ifdef for until
we can break binary compatibility
(osl_detail_ObjectRegistry_getMutex() gets a warning with Clang that can be
cleanly fixed only by breaking binary compatibility).
Do we have something for either of these?
--
Lubos Lunak
l.lunak@suse.cz
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.