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

List:       kde-core-devel
Subject:    Re: Keeping binary compatibility
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2010-10-05 19:01:05
Message-ID: 201010052101.05814.neundorf () kde ! org
[Download RAW message or body]

On Monday 04 October 2010, Lubos Lunak wrote:
> On Monday 04 of October 2010, George Kiagiadakis wrote:
> > On Sun, Oct 3, 2010 at 10:32 PM, Alexander Neundorf <neundorf@kde.org>
>
> wrote:
> > > What about source compatibility ?
> > >
> > > At least for kdelibs we try to guarantee source compatiblity of the
> > > cmake files.
> >
> > I think source compatibility is easier to maintain because it is more
> > obvious when you break it and people generally understand it better
> > than binary compatibility. I don't think we have a problem keeping
> > source compatibility atm, do we?
>
>  We occassionally do (I e.g. remember fixing a bug somewhen in the past
> that had been introduced by broken source compatibility and people thinking
> 0 is a null pointer).
>
>  But I agree that generally this is a much smaller problem because usually
> the problem simply shows up, shows up in a less confusing way, shows to

Wrt to cmake files, it's at least not obvious to many developers how they can 
break SC (http://techbase.kde.org/Policies/CMake_and_Source_Compatibility)

> more knowing people, and, last but not least, I doubt there's a sane way to
> having any good checks for that anyway.

Ok. My actual question was: do we guarantee SC ? 
Only for kdelibs or also for other modules ?

Alex

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