Re: [Tads3] 'inherited' and propNotDefined

[BrenBarn@xxxxxxx]

Mike Roberts wrote:
-----
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?
-----

       This seems fine to me.  I imagine there's little or no existing code that would be affected by this -- my impression is that propNotDefined isn't used a lot except in funky meta-stuff like Kevin Forchione's Proteus.

-----
class A: object
  propNotInherited(prop, [args]) //...
;
class B: A
  propNotInherited(prop, [args]) //...
  xyz(x) { return inherited(x); }
;

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.
-----

       That sounds good.

--OKB