[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Binary compatibility required for KOffice Libraries?
From:       David Faure <dfaure () klaralvdalens-datakonsult ! se>
Date:       2003-01-17 10:14:34
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 17 January 2003 15:40, Clarence Dang wrote:
> Hi,
> 
> Is it neccessary to retain BC for the koffice/lib/ (like it is with KDE)?
> I ask this because I want to make some fixes to KoRuler that will easily break 
> binary compatibility (don't worry I'll fix KWord/KPresenter too) and also 
> with KoVariableSettings, displayFiedCode() and setDisplayFiedCode() look like 
> they need renaming...

My take on this was: let's keep BC in kofficecore and kofficeui (those are used
by some 3rd-party KOffice applications); let's however break BC in libkotext
(we've already done so. This lib isn't meant to be finished anyway).
So no problem for KoVariableSettings.
For KoRuler, isn't there a BC way to fix it?

- -- 
David Faure -- faure@kde.org, dfaure@klaralvdalens-datakonsult.se
Klarälvdalens Datakonsult AB, Platform-independent software solutions
Contributing to: http://www.konqueror.org/, http://www.koffice.org/
KOffice-1.2.1 is available - http://download.kde.org/stable/koffice-1.2.1/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+J9eK72KcVAmwbhARAiMyAJ9gTvRk53QzrTKQNzarwLVSITmJmACffubQ
6PGpvNaybIVGdCq72p6qyis=
=SQeB
-----END PGP SIGNATURE-----

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]