On Fri, 2008-05-09 at 20:01 +0200, Mathias Bauer wrote: > A warning to everyone committing such cleanups to cvs: please use > "non-pro" builds on at least one platform
Indeed. The unused methods are always pulled from a .pro build. The same issue arises with stuff used only on one platform but included in all platforms, e.g. some ole2 stuff under windows. > Another interesting discovery was that removing ctors can be dangerous > at times because some compilers automatically create default or copy > ctors for classes even if they aren't used. ... I found this problem mainly > in "binfilter" - a fact that doesn't surprise a lot. Yeah, given the rather poor state of standalone C++ parsing frameworks the current mechanism is a somewhat horrific (but functional) scraping of the output gcc assembly stage. The output data is correct, but there is the limitation that it's not easy to tell that a specific ctor of a range of ctors is unused vs that objects of that class are impossible to actually create at all even if other code accepts pointers to such objects and call methods on them. FWIW http://people.redhat.com/caolanm/GoOOoCon08.odp has some brief notes on it. C. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
