[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: Marc Mutz <Marc.Mutz () uni-bielefeld ! de>
Date: 2001-07-14 15:27:24
[Download RAW message or body]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 13 July 2001 16:25, Lars Knoll wrote:
<snip>
> 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.
<snip>
Actually, I think we should break SC at quite a few places:
(some things I remember in random order)
- - QRegExp3 is significantly different from QRegExp2 and in a way that
is uncheckable by a compiler (regexp syntax). Also, QRegExp's are used
in quite a few places implicitely. E.g. this small, innocoent-looking
line will break:
QString str("Hello (World)!");
str.replace("(World)", "World");
because arg0 or QString::replace is actually a QRegExp....
- - KRegExp should be nuked in favour of QRegExp3.
- - KProcess should be nuked in favour of QProcess
(Qt multi-threading should also at least be be considered though I
personally don't see a need for it)
- - I don't know much about this stuff, but it seems KDE uses a custom
libloader where we should use Qt3's for KDE3 instead.
- - KDE's KPart's need to be ported to QLibrary, QPluginManager et al.
- - KDE's KConfig should be replaced by QSettings
- - ...
At least the KPart and KConfig changes should be pretty deep if we want
to make use of the full Qt3 potential in that area. And they affect a
very large part of the core source code base.
Marc
- --
Marc Mutz <Marc@Mutz.com>
http://marc.mutz.com/
http://www.mathematik.uni-bielefeld.de/~mmutz/
http://EncryptionHOWTO.sourceforge.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7UJbZ3oWD+L2/6DgRAno5AKDtQATJ5uavcH5/+7eUG+NlRGykpgCg7p3t
ZxWloqP8W0G2gmeYoOt3gfs=
=lnPu
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic