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

List:       kde-core-devel
Subject:    new libkab - when to incorporate?
From:       Mirko Sucker <mirko.sucker () unibw-hamburg ! de>
Date:       1999-11-21 20:52:45
[Download RAW message or body]

Hello all,

as I announced at Erlangen, I worked on a rewrite of the kab library. Main
reason was to get rid of the string class shipped with the STL that first led
us into compilation problems and second does not interact well with Qt unicode
strings.
Another major goal was to get the lib much smaller and more efficient than it
was before. 

You know that there is more development on PIM software done in the CVS module
pim. But since KRASH is announced, we must get something working into the KDE
distribution. 

Here are some points to compare both implementations:
° Confusion: Getting rid of the STL string class is merely important, in my
opinion. Since the STL string class did not make it into the standard, and does
not support UNICODE, it has been replaced by QString.

° Code size: While the old library consists of 25 (!!) source (and according
header) files, the new one uses 3 (in words: three). The bloat of the old
implementation steemed from splitting an application into an interface and a
binary that was not designed therefor. The new one is. 

° Design: The new one is better, of course :-)

So, my question is: May I commit this change? I think it is merely important to
do it before KRASH is released. Everything compiles well on Intel-Linux
machines, and there are no more "special features" like the string class that
create problems when porting to other systems.

Sorry for the long time to get it done. It was far more complex than I expected
:-|

Waldo?

Greetings,
--Mirko.
-- 
Denn der  Mensch  liebt und ehrt den  Menschen,  solange er ihn
nicht zu beurteilen vermag, und die Sehnsucht ist ein Erzeugnis
mangelhafter Erkenntnis. (Thomas Mann)

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