On Fri, Oct 31, 2008 at 8:38 AM, Ville M. Vainio <[EMAIL PROTECTED]> wrote:
> I'm not convinced it's a good idea when there are so few concrete > implementation of the concrete classes. IMHO, abstract base classes > are handy when the end users will be creating the concrete classes, > otherwise it drifts dangerously to the area of over-engineering > without real benefits to code quality. The unit tests in question have failed often enough to prove their usefulness. I'm not proposing this in a vacuum. The qt plugin would have benefitted significantly from a formal definition of what is expected of wrapper classes. At present, my implementation approach is to wait for AttributeErrors. That isn't good enough. > On a related note, you may be interested in python2.6 abc module: Thanks for the link. I'll study it carefully, both for pros and cons. > http://docs.python.org/dev/whatsnew/2.6.html#pep-3119-abstract-base-classes Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
