On 15/02/12 21:31, Kate Goss wrote:
Hi Michael, Caolan,
How accurate/ up to date is unusedcode.easy? Is there a way to make sure
the methods I'm removing are genuinely unused?
the problem is that unusedcode.easy is generated from a single
configuration of LO. because there is a huge number of potential
configurations, there may be some false positives, especially in modules
that are highly platform dependent, such as "vcl", "tools", "sal" or
"extensions".
Am I just doing it wrong and removing the wrong things? : )
you could try to "git grep" for the function you want to remove, and see
if there's anything that calls it behind some #ifdef or in some platform
specific code, but it's not a huge problem if you miss something, that's
why we review patches :)
regards,
michael
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.