Hi Doug:

>From dougo@ccs.neu.edu Fri Oct 17 14:22:32 1997
>From: Doug Orleans <dougo@ccs.neu.edu>
>To: Johan Ovlinger <johan@ccs.neu.edu>
>Cc: lieber@ccs.neu.edu, dem@ccs.neu.edu
>Subject: Re: overriding instance variables
>
>Johan Ovlinger writes:
> >   Karl:
> >   >At the level of object graphs and at the level of simple class graphs
> >   >there is only one d-part. 
> > 
> >   Hrm, I didn't think so (not sure: This point always confuses me)
> > 
> >   imagine an object with the structure:
> > 
> >   A : B *common* <c> C.
> >   B = <c> D.
> > 
> >   I believe that methods attached to A will see the C version of c,
> >   whilst methods at B get the D version. If this is true,
> >   then our object graph also includes the <c> edge (even though it can't
> >   be see from within B). 
>
>This is indeed true (according to the semantics of Java), except that
>the <c> C edge can actually be seen from within B, using
>
>    super.c
>
>or
>
>    A.c
>
>I find this really confusing and not very useful; I wish there were an
>annotated Java reference manual that explained the motivation for
>design decisions such as this one...
>
>--Doug
>
Yes, that is indeed confusing. Good we don't support overriding of parts.

-- Karl