How about "pure virtual methods"?
Mike Meyer
mwm at mired.org
Tue Dec 21 22:17:22 EST 2004
More information about the Python-list mailing list
Tue Dec 21 22:17:22 EST 2004
- Previous message (by thread): How about "pure virtual methods"?
- Next message (by thread): How about "pure virtual methods"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Noam Raphael <noamr at remove.the.dot.myrea.lbox.com> writes: > The answer is that a subclass is guaranteed to have the same > *interface* as the base class. And that's what matters. This is false. For instance: class A(object): def method(self, a): print a class B(A): def method(self, a, b): print a, b B implements a different interface than A. Statically typed OO languages either use multi-methods or disallow changing the signature of an overridden method. A tool to detect such cases would probably be almost as useful as the tool you've proposed. <mike -- Mike Meyer <mwm at mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
- Previous message (by thread): How about "pure virtual methods"?
- Next message (by thread): How about "pure virtual methods"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list