Issue 86384

Created attachment 51675 [details]
patch to remove unused code

Caolan, when looking on the patch I wonder how the tool you are using treats
virtual methods. Does it exclude them from the list of candidates for unused
methods?

Yes, it explicitly detects and ignores virtual methods, the name of the game
isn't to detect all unused and uncallable code, but to give a list of guaranteed
uncallable methods. And I can't think of an easy way to ensure that a given
virtual method can never be called, though in theory I guess we should be able
to see that given an entire hierarchy of virtual methods that a given slot could
never be called and that all the virtual implementations of that slot are worthless.

At least in case of UNO objects it is impossible to detect whether they are
used. APIs of UNO objects may not be used inside OOo code at all but in fact are
needed as part of the whole OOo API to be accessible from scripts. But if
virtual methods are excluded we are safe here.

Carsten, please take over.

cd->sb: Please have a look at the patch from Coalan as you made several changes
regarding layering in the desktop project.

cd: Target OOo 3.0 should be Ok.

@cd: It appears there is no overlap between files touched on CWS sb83 and the
attached desktop.unusedmethods.patch.

@jl: Maybe you want to have a look at the changes to desktop/source/deployment
in the attached desktop.unusedmethods.patch.

jl->cd: I cannot see any problems at a first glance. Go ahead applying the
patch, but let jsk test very thouroughly the extension manager.

cd->cmc: I wasn't able to apply your changes to pages.hxx/pages.cxx as the
removed methods are used by DEV300m1. All other changes are ok.

cd: Revised patch applied.

cd: Verified.

seen in master