Thanks, Bill.

Yuriy.

"Bill McCormick" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> BaseClassA forms an IsA relationship with the subclass. Any other
> superclasses do not form this relationship. This is fairly standard for
> all object oriented db's. All other super classes only inherit their
> interfaces.
>
> Yuriy Toropov wrote:
>
> > Ramon,
> >
> > I found this in Cache documentation as well.
> > In this case Cache's multiple inheritance mechanism is really limited if
I
> > can't use instance of subclass as instance of one of its superclasses.
This
> > really breaks Object Orientation, don't you think?
> >
> > Thanks,
> > -Yuriy.
> >
> >
> >
> > "Ram�n Jim�nez" <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]
> >
> >>Hi, Yuriy,
> >>
> >>When working with multiple inheritance, there are a couple of simple
rules
> >>to keep in mind:
> >>
> >> - Storage will come from the first (reading left to right) class in the
> >>superclass list
> >> - If one method exists in more than one superclass, the subclass will
> >>inherit the implementation of the last (rightmost) class in the
superclass
> >>list
> >>
> >>Since BaseA and BaseB are independent, their storage is set up so that
> >>instances of BaseA go to ^User.BaseAD and instances of BaseB go to
> >>^User.BaseBD. Subclass lists BaseA as first superclass, so its instances
> >>will go to ^User.BaseAD and thus querying on the User.BaseB extent
yields
> >
> > no
> >
> >>results.
> >>
> >>This is the behaviour - whether bug or feature is still open to
discussion
> >>:)
> >>
> >>HTH,
> >>
> >>Ram�n
> >>
> >>
> >
> >
> >
>
>
> -- 
> Bill McCormick
> Web/Objects Support Manager
> InterSystems Corporation
> [EMAIL PROTECTED]
>



Reply via email to