Hi Ken, Are there any real benefits to using abstract classes between one's > immediate subclasses of all VFP controls, and one's first layer of concrete > classes, in VFP? If so, what are they? >
No, usually not. In most cases it's another case of adopting a practice that is valid for other languages even when it's not appropriate in Visual FoxPro. Empty classes in VFP make sense when you are providing code to third parties as a framework vendor or tools provider. In these cases they provide developers with a place to put customizations of the framework without resorting to complex strategies. They are also useful if your users create a lot of specialized subclasses and you want to ensure that certain methods are always callable or properties are guaranteed to be there. In most other cases I've come across they are merely there "just in case" or because "it's good OOP practice". Can't comment on Python or Dabo. -- Christof --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAL4QJhhrzHD0F6mNo5tXq-KSvwyiVDdZT9fVXJU=ypnpq+4...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
