binary compatibility issues in kdelibs

Michael Goffioul goffioul at imec.be
Wed Jul 10 09:03:33 BST 2002


> > Those 2 classes are not intended to be used by 3rd party applications
> > and to my knowledge, they are not used. The headers are only installed
> > to allow me to split KDEPrint between kdelibs and kdebase (and maybe
> > other locations). But those classes are only really used by KDEPrint.
> > So if you upgrade simultaneously kdelibs and kdebase, you shouldn't
> > get any problem. The only real "public" header is kprinter.h, which
> > I think is still BC.
> > Anyway, if this is a problem, I can revert the changes and remove the
> > added features.
> 
> I guess that is okay. Might be worth adding a note to the header
> file like TT does and possibly marking the class as @internal.

It's OK for me. However this may be done for many installed KDEPrint
headers. The only headers that may be possibly used by other apps
are:

kprinter.h
kprintaction.h
kdeprint/kprintdialogpage.h
kdeprint/kiconselectaction.h
kdeprint/kpreloadobject.h (I doubt it might be the case, but...)
kdeprint/kprintdialog.h (idem)

All other are installed by convenience and should be marked as
internal. I don't use Linux these days, and I will be on
holidays for the next 2 weeks, so if anybody would like to
do the change for me, it would be nice.

Bye.
Michael.

-- 
------------------------------------------------------------------
Michael Goffioul		IMEC-DESICS-MIRA
e-mail: goffioul at imec.be	(Mixed-Signal and RF Applications)
Tel:    +32/16/28-8510		Kapeldreef, 75
Fax:    +32/16/28-1515		3001 HEVERLEE, BELGIUM
------------------------------------------------------------------




More information about the kde-core-devel mailing list