On Wed, 2012-02-08 at 20:33 +0100, Stephan Bergmann wrote:
I guess one can argue both ways here. A feature-complete basegfx
library where some features happen to only be used in certain scenarios,
but the library itself clean of scenario-differentiating ifdef hacks vs.
"micro-level configuration management."
If an inline is unused it doesn't appear, seeing as gcc doesn't generate
code for unused inlines. And if something is only used by a cppunit test
then it doesn't appear either seeing as calls to the code are
generated ;-)
So there are some alternatives options to hide something from
callcatcher. Remove it, ifdef it out, convert it to an inline, write
unit tests that call it, add it to the sed line that differentiates
unusedcode.all from unusedcode.easy
C.
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.