On Mon, 2011-11-28 at 09:03 +0100, Stephan Bergmann wrote:
VOS_NAMESPACE etc. stuff, e.g.), we will likely need macros for new
features that can be enabled for compilers that already understand them,
without breaking the code for legacy compilers.
I believe the Mozilla guys augment this stuff by having an LLVM plugin
that does the validation of the keywords on top of the compiler. That
seems like a sensible approach to me.
On the other hand; I'd (personally) prefer to use some defines to
create the 'override' and 'final' keywords (as they will be in future).
Defining them to 'virtual' or even empty would do, if they are not
present in the compiler. cf. glib's provision of a stock 'inline'.
That should help reduce code thrash, and hideous ugliness ;-) keeping
us closer to more readable, standard C++.
HTH,
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
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.