Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Vfp vs Vb
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00283708
Message ID:
00284509
Vues:
29
>Yes but you create a instances off all the parents.

There is no parent. I merely implemented the interface of another class and borrowed its behavior. I don't claim to be simulating inheritance here. If anything, I am doing something that is more akin to patterns...

>In VFP you must only create a instance of the class you want to use . This is for me a major difference
>

Yes, there are two instances here. One, the class that I am actually work with. And two, and instance the class creates. The internal instance however, is hidden from me during implementation. I claim that in the end, it is not that big of a difference.

>You need to know in VB who are the parent's !

You need to know it in VFP as well, especially when you are looking for code.

>This scheme is ok when you have components ( complex objects ) as 'parent' class. So I think the VB OO is enought in a COM world but a can't really figure out to rebuild my applications that way.
>

Nobody is telling you to rebuild your applications. As far as fitting into the COM world, think for a moment about what you said here. Where is the rest of the world headed? COM right? I think I like my odds in learning how OO is implemented on that side of the fence <bg>.


>Every morning when a wake up I don't wan't to call and wake up all my familly to start my job.
>Ok maybe I need to call my english teacher when I write english !

This analogy has no relevance whatsoever...<s>.


>>I may not want to inherit the behaviors. I do however, want to keep the interface constant. In VFP, we really do not have a way of doing this.
>

>Abstract class ?

No... Look at what I said. I may not want to inherit the behaviors, just the interface. VFP's method of abstraction is achieved through inheritance. Any implementation code I place in the abstract class will automatically be inherited by its subclasses. This may or may not be desireable. Look at interface implementation as being somewhere in the middle of having and not having inheritance. It is a feature I wish we had in VFP. In many ways, this is what the whole patterns movement in VFP is all about...
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform