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

List:       kde-core-devel
Subject:    Re: What to do after 2.2?
From:       Ralf Nolden <nolden () kde ! org>
Date:       2001-07-13 16:23:38
[Download RAW message or body]

Martijn Klingens wrote:
> 
> On Friday 13 July 2001 16:25, Lars Knoll wrote:
> > Binary compatibility would be broken by such a step anyway, and is actually
> > rather unimportant. Source compatibility is what matters, and I'm pretty
> > confident we can do such a move without breaking source compatibility in
> > more than one or two places.
> 
> Would it be possible to provide a set of stub functions that emulate the 2.x
> API that are _not_ source compatible in a libkde2emu or so? That way no
> porting at all is probably necessary. Note: I don't have any serious
> knowledge on this subject, I really don't know against what obstacles one
> would run when trying this. Also, I don't know at what particular places
> source compat will be broken (except for the style engine, but that's not a
> really big problem - I'm looking forward to the new one anyway).
> 
> Could someone explain in short if such a lib is possible and if not
> (probably), why? Like many other people in the previous mails, I'm not
> that much concerned about BC, but all the more about source compat.

Like Lars said, source compatibility will be provided to the maximum. An
additional lib for compatibility even if possible would cause you more
headaches in the future. A clean cut is needed there and the little
effort to be put into porting sourcewise is worth it. Even large
projects have been already ported in hours to Qt 3 (see the Qt
mailinglists and the kdevelop mailinglists).

Ralf
--
We're not a company, we just produce better code at less costs.
--------------------------------------------------------------------
Ralf Nolden
nolden@kde.org

The K Desktop Environment	The KDevelop Project
http://www.kde.org		http://www.kdevelop.org

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