[lazarus] compile error on New Sources from cvs - FIXED

[Marc Weustink]

At 23:49 27-11-2003, Mattias Gaertner wrote:
>On Thu, 27 Nov 2003 23:40:38 +0100  Marc Weustink <marc at dommelstein.net>
>wrote:
>
> > At 23:24 27-11-2003, Mattias Gaertner wrote:
> > >On Thu, 27 Nov 2003 23:10:24 +0100  Marc Weustink <marc at dommelstein.net>
> > >wrote:
> >
> > [snip]
> >
> > > > I don't think this is the way to go. Now, if the interface gets
> > > > extended with mode direct calls, we can add a TBase... for every
> > > > TComponent/TControl etc we need.
> > > >
> > > > OK, what happened.
> > > >
> > > > The LCL needs the baseinterface..
> > > > The baseinterface needs the LCL..
> > > >
> > > > That means problems. Sure you can introduce all kinds of base classes,
> > > > but
> > > >
> > > > how would you do this with a TBaseControl and a TBaseWinControl ?
> > > > If we are going to introduce dedicated interface classes, it starts to
> > > > look like a discussion we had a few years ago.
> > > >
> > > > Seen the latest problems and implications, I wonder if we should
> > > > continue the last changes we made. IMO, we should undo it and try
> > > > another route.
> > >
> > >What about replacing TBaseMenuItem with TComponent?
> >
> > Hmm...
> >
> > That would require a lot of typecasting, but is better.
> > The new situation would be
> >
> > The LCL needs the baseInterface and FCL
> > The baseInterface needs FCL
> > The XXXInterface needs LCL and baseInterface and FCL
> >
> > I don't see a problem here.
>
>No wonder. It is the old situation. :)

Nah, not complete. In the old situation an internal interface object 
(handle) was passed.

>I will change it ...

OK.

Marc