Removing Unused Code in LibreOffice
Jan 12, 2012, 20:00 (0 Talkback[s])
(Other stories by Michael Meeks)
No-Size-Fits-All! An Application-Down Approach for Your Cloud Transformation REGISTER >
"It seems that over half of our unused code has now bitten the
dust. Unfortunately as we remove more, more wasteage tends to be
revealed, which explains some of the upward jumps in the graph,
nevertheless the trend is clearly down. One of the side benefits of
the unsung heroes working at the conversion of our old-style macro
driven generics to modern STL is that this looses us several unused
methods per class converted.
If you want to get involved with LibreOffice development, it
doesn't get much easier than this - please do check out the code
and have a go. For the more adventurous finding an unused
destructor, without a matching unused constructor is proof of a
leak that needs chasing, of which there are a handful.