No. The only exception is subclassing, but you shouldn't subclass
unless it is in fact your intention. If a Valve needs to contact an
Engine, then the Valve needs a reference to the Engine. It doesn't
really matter that there is an array of Valves in the Engine – that
kind of referencing only goes in one direction.
HTH -
Andrew Keller
On Oct 30, 2008, at 10:53 AM, Sam Rowlands wrote:
Is there a way to create a class.parent without having a property on
the class?
For instance say I have a class called Engine, then I have an array
of Valve classes. The array is a property of Engine.
Engine.Valves()
However now I want the valve to communicate with the Engine, to
notify the engine when it fails, do I create a property on the valve
class called parent and set that to be my engine, or is there some
fancy trick I can use to probe the valve and figure it out?
Have a Great Week :)
Sam Rowlands
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|