On Tuesday, December 14, 2010, John Layt wrote: > Now, I've introduced some private functions in the 4.5. and 4.6 that may
that's the problem right there, really: never, ever introduce private functions in public libraries. that's what we have dptrs for: add them to the private class and access them there from the public class' implementation. > "[You can] remove private non-virtual functions if they are not called by > any inline functions (and have never been)." nobody should be using private functions, so it becomes a moot point. at least that's been how we've been dealing with that issue up until now: apps that violated private member encapsulation deserve to break. ;) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
