Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
CreateObject() vs NewObject()
Message
De
26/08/2007 15:44:28
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
 
À
26/08/2007 14:48:25
Mike Yearwood
Toronto, Ontario, Canada
Information générale
Forum:
Visual FoxPro
Catégorie:
Classes - VCX
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP1
Divers
Thread ID:
01249678
Message ID:
01250513
Vues:
32
>>>Picky, picky! ;) I'm only trying to use some pseudo pseudocode to say "detect if the specified vcx file name is already opened/available/whatever" which in this case is easier said in code.
>>>
>>>How about "\VCXNAME.VCX" $ SET('CLASSLIB')
>>
>>But then your factory can know not only the name of the class to use, but the location of the classlib as well - it can be stored in factory.dbf. So you only need to know the name and location of the class once, when you create the record in factory.dbf.
>
>Absolutely. That's the point of the abstract factory.

And (don't you feel the deja vu creeping in?) the difference between abstract factory and a concrete factory is?

>> No Set ClassLib/Procedure at all.
>
>The factory would have to issue these.

If factory uses newobject() then it doesn't need these at all. Both lists can remain empty.

I see a different problem with factory: it returns an object, which then needs to be assigned to something. It can't replace this.addobject() and this.newobject(), unless we pass This as a parameter. Does your factory do that?

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform