Crazy idea time.
I wonder, as the set of configuration parameters from the source tree in a
specific build is fixed, would it be possible to simply generate a large
(C++) struct containing all of them, populate one global such struct
variable on startup (or even at build time with the default values, then
just replacing ones that are modified by user at startup time), and have
those officecfg::* calls simply refer to fields in that struct? Would be
vastly faster than current code, and simpler (at run-time) than Michael's
idea.
Sure, would have the non-ideal effect that any modification to the
officecfg module would require recompilation of any code that calls
officecfg::....
--tml
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.