kicker/taskmanager classes have d-pointers,files installed

[Lubos Lunak]

On Wednesday 30 of July 2003 11:12, Marc Mutz wrote:
> On Monday 28 July 2003 15:41, Lubos Lunak wrote:
> >  the subject basically says it all. Classes in the
> > kdebase/kicker/taskmanager kicker's internal library have d-pointers,
> > thus suggesting this lib is supposed to stay BC, but it actually
> > doesn't have .h files installed, so BC doesn't make any sense there.
> >
> >
> >  Will anybody mind if I remove the d-pointers, and while I'll be at
> > it, also break the BC a bit (since I have no other idea how to fix
> > something there) ?
>
> Not knowing the code, this might just be the bridge pattern employed to
> reduce #includes in header files, reducing inter-.cpp file depedencies
> and thus compile time?

 No. The only place where the private classes are refered to are the 
d-pointers member definitions themselves. It's clearly that somebody wants to 
make it BC, for some strange reason.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/