--nextPart1188776.JJjmnaCxTy
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Mittwoch, 1. Dezember 2004 20:32 schrieb Willy De la Court:
> > > the version 1.114.2.2 which is tagged KDE_3_3_1_RELEASE has no setIcon
> > > and version 1.114.2.3 tagged KDE_3_3_2_RELEASE has the setIcon functi=
on
> > >
> > >
> > > hmm strange if i recall correctly this breaks binary compatibility

Why should it? It would be bic if it were the other way round.

Yet we can argue whether it is allowed to introduce new public symbols in=20
patchlevel releases.

> >
> > You caught me. =A0It's true. =A0I built these recent packages against
> > kde-3.3.2 (due to be released real-soon-now). =A0Bummer that
> > bin-compatibility was broken.
> >
> > Is it worth filing a bug? =A0Dunno if they'll even consider it a bug.
> > Qt/KDE has always maintained forward compat (stuff built on/for qt/kde

Qt promises forward and backward compat between patchlevel releases. I've=20
never read or heard anything about KDE guaranteeing forward compatibility=20
between patchlevel releases.

> > 3.x.y will/should work with qt/kde 3.x.(y+1) ) but not necessarily
> > vice-versa.

What you described here is backward compatibility.

mfg
 Leo

--nextPart1188776.JJjmnaCxTy
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBriVhj5jssenUYTsRAqNmAJ4sCSZP3x56/sFiixBP0uEV/0ZjXACfaaKH
Ysu606GfL2AllAlOmnvzFQQ=
=Ppvk
-----END PGP SIGNATURE-----

--nextPart1188776.JJjmnaCxTy--