Re: [Tads3] 'inherited' and propNotDefined

["Mike Roberts" <mjr_@xxxxxxxxxxx>]

BrenBarn@aol.com wrote:
> If no such method is found, propNotDefined should be called on the base 
> class,
> because that's where we were looking for the inherited method.
Just in case I wasn't clear (which is quite likely, since I'm finding this 
to be a pretty slippery thing to get my hands around), that's my proposal as 
well.  My thinking was that propNotDefined should be "inherited," as though 
we were running propNotDefined to start with.

> I do, however, agree that it would be better to avoid a separate
> propNotInherited and stickwith propNotDefined.
That's the way I'm leaning as well - as Jesse pointed out, if we had 
propNotInherited, we might need propNotDelegated as well for completeness, 
and that just seems like too much.

--Mike

_________________________________________________________________
Need more e-mail storage? Get 10MB with Hotmail Extra Storage.   
http://join.msn.com/?PAGE=features/es