-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of Jon A. Cruz Sent: donderdag 8 november 2007 18:43 To: Engelen, J.B.C. (Johan) Cc: inkscape-devel@lists.sourceforge.net; niko@...1267... Subject: Re: [Inkscape-devel] Methods hiding others
I think the main factor is overriding *some* methods with the same name. "With the same name" is the key part.
As I understand from the faq: Overriding a method with the same name is okay, as long as that function was not overloaded in the base class. If it IS overloaded, it will *not* be overloaded for the derrived class, i.e. all calls will go to the derived class' function. So if you have function overloading (as "conveniently" done in LPE), you must override all overloaded functions.
I'd not looked to closely, but some cases of this are from signatures not matching completely. I believe one odd case I've fixed had a const mismatch where one of the base/subclass methods was declared a const method and the other was not.
The other really bad case is when you pick a name for something new in your subclass that was already used in a parent class. Then you get the same name, but used for different purposes. Very confusing.
I'm certain that I did not do that (if I did I must have been sleeping), because indeed that is very very confusing and error prone. :)
But, did my change to LPESlant work? Is the warning gone for LPESlant?
Johan