On Apr 12, 2006, at 7:47 AM, CV wrote:
Edit: I meant to say: Super.Constructor only works if Constructor
is the name of the superclass's constructor,.... in 2006r1 and prior.
Jack
You can have both if you implement both
And the super can, in either its constructor or method with the name
of the class simply call "the right one"
Suppoer your super class is class1.
Constructor
// do actual constructor stuff
Class1
Constructor()
Then it doesn't matter how your subclass calls the super's constructor.
Some quick testing leads me to believe that RB invokes the
CONSTRUCTOR version when creating instances with NEW so that seems to
be the preferred one.
And, the ones that are named the same as the class do need to be
updated IF you change the name of the class. This is just another
reason to prefer the one called Constructor.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
