On 5/29/13 8:28 AM, Ken Dibble wrote: > Question 1: > > 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?
I don't think so, but I'm rusty with VFP. I guess it's kind of painful in VFP to reparent visual classes (coded classes is easy because you can just search and replace the old parent class name with the new). Now that I say that, it's therefore easy with visual classes too because you just find/replace in the .vcx class library table. But you if I remember correctly it isn't easy if even possible via the IDE. > Question 2: > > I am probably going to migrate my code to Python in the next 4-5 years (or > maybe to > some similar language that doesn't exist yet; right now the goal is to be > able to use > Dabo for development). Python has multiple inheritance via mix-ins. However, > based on > my limited understanding, this looks like full code inheritance, not just > interface > inheritance. Assuming that's true, is there any benefit to using abstract > classes in > Python in general? With Dabo in particular? I've never found any benefit to creating abstract classes you have no immediate need for in Python or Dabo. If you find you need one, you create it at that point, but not before. Paul _______________________________________________ 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/[email protected] ** 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.
