On Monday 17 of September 2012, Norbert Thiebaud wrote:
On Mon, Sep 17, 2012 at 3:27 AM, Stephan Bergmann <sbergman@redhat.com>
wrote:
and for another,
I think there currently is nothing in config.h that makes it extremely
problematic if it happens to not be included first thing into some
compilation unit
That is a flaw, when you want a heder to be first, you got to make
sure that you can't forget about it :-)
, so enforcing it by modifying hundreds of files probably is
not worth it right now.)
Well, it is like saying... we have thousand of warnings... so
contemplating -WError is not worth it...
that is a self-fullfilling prophecy...
I admit I have no idea what this dicussion is actually about, but I think
that all compilers we support have some kind of -D for globally introducing a
#define and -include for #include at the beginning of files.
I could understand the desire for some lo.h from the point of view of
performance (though the relevant sub-headers will probably manage to stay
in main memory anyway)
And this, I think, is called either precompiled headers, or smart compiler,
neither of which need to be reinvented.
--
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.