Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Foxpro v/s Access
Message
From
09/06/1999 14:59:32
Guy Pardoe
Pardoe Development Corporation
Peterborough, New Hampshire, United States
 
General information
Forum:
Visual FoxPro
Category:
Internet applications
Miscellaneous
Thread ID:
00226230
Message ID:
00228072
Views:
25
Regarding http://www.bowdoin.edu/~csaunder/programming/siminherit.html

Maybe I'm missing something but it seems to me that you could make a good argument that FPW2.6 was object oriented too. Except for the construct of the class/object. You can make a psuedo object with a FUNCTION and govern it's properties with variables scoped public or private, and create methods with other function calls. You can control inheritance through the calling tree. (YAG's Codebook 2.6 made use of this to a certain degree.)

Sure it's a stretch. And you don't have proper encapsulation, etc. But you could make the argument.

I've read articles from advanced (I suppose) VB programmers trying to make the argument that you can get VB inheritance by intercepting the [Windows-level] messages between the objects and taking over control of the messages. I don't mean to be rude to such authors but that is, for the most part, rediculous!

As a collective body of programmers, most VB people aren't going to take the time to [in effect] learn C/C++ and all the little gotchas that go along with Windows-level messaging between objects/containers. VB is for helping programmers be productive without having to bother with that minutia.

In fact, as I read these articles I thought the correct term for this is: VBC. Now VBC is not a language. It's a technique, maybe even a life-style, requiring VB developers to go way above the normal learning curve for their tool of choice in order to take advantage of subclassing and inheritance. Some of the authors advancing this idea were open enough to say things like, 'you will experience "spectacular crashes" as you begin to implement these techniques.' (That is amost verbatim.)

Anyhow, I don't mean this as a put down to VB, or VB programmers. VB really is a fine tool and it's getting better as the years go by. (In spite of its history as [probably] the most popular legacy language on the Intel platform.)

Believe me, I don't want to start a holy war over Fox/VB. For VB programmers though, sub-classing & inheritance appears to be an issue that won't be resolved any time soon.

Guy
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform