[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tads3] 'inherited' and propNotDefined
- From: "Søren J. Løvborg" <kwi@xxxxx>
- Subject: Re: [Tads3] 'inherited' and propNotDefined
- Date: Thu, 11 Sep 2003 13:24:49 -0000
- To: <tads3@xxxxxxxxxxx>
> Does anyone see a problem with changing the way 'inherited' is processed so
> that propNotDefined is fired if there is no inherited definition of the
> method?
Okay, you lost me.
> (... ... ... ...)
> When we call B.xyz(), I think we'll want to invoke A.propNotInherited(), NOT
> B.propNotInherited(), because the search for the inherited xyz() would start
> with A, not with B.
Okay, this I can follow, and yes.
That's the behaviour I'd expect.
Søren J. Løvborg
kwi@it.dk