Outer class reference oddity?
An
d at home.com
Fri Aug 23 20:55:13 UTC 2024
On Thursday, 22 August 2024 at 18:39:09 UTC, Walter Bright wrote:
>
> Generally speaking, when there are multiple lookup paths, the
> inevitable result is confusion.
>
> I spent a lot of time working out how nested classes and nested
> functions work. I'm a bit afraid to start messing with the
> semantics of it at this point.
>
Lookup should perform from nearest to farthest
for class hierarchy
from inside its self
from its' derived class
from its' outer class
from its' outer derived class
for function
from inside its self
from its' outer function
if it is a aggregate function -> use above class hierarchy rule
More information about the Digitalmars-d
mailing list