Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SubClasses and parent classes at compilation
Message
From
22/12/1998 09:46:28
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Title:
SubClasses and parent classes at compilation
Miscellaneous
Thread ID:
00169625
Message ID:
00169625
Views:
54
Hi Everybody

I'm reading Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides's book, Design Patterns.

It makes me wonder some questions. The focus is not actually on VFP, but I imagine that the system is about the same.

I read that a subclass (not the instantiated object) and its legacy are defined at compilation. Does it mean that this subclass is compiled as a whole, including both its own 'by exception' code/properties and the inherited code/properties (when not overriden)?

Or is it still compiled as a subclass (as we see it during coding), that will remain separate and dependant of its parent classe and will call it when it is instantiated?

In other words, in the first case, when compiled, the subclass doesn't need anylonger its parent class to be instantiated. Thus I should be able, in an application, to SET CLASSLIB to the library containing my subclass without SETting CLASSLIB to the library containing the parent class if they are different. And If I don't need this 'parent/base' library, I can generate smaller an .EXE, not including it.

My classlibs are hierarchized as general purpose base libraries, and 'sub' specific to application base libraries. I would be great if I can only include the second one in my application.

Can you tell me how it works exactly?

Thank you for your soon (and complete? :-)) answer.

Kind regards

Philippe
Kind regards

Philippe RIONDEL,
a French man in Montreal
=======================================================

Who tries can sometimes be wrong, who doesn't is always

Next
Reply
Map
View

Click here to load this message in the networking platform