API problems (Was: future versions)

[Frans Englich]

On Friday 06 February 2004 16:22, Waldo Bastian wrote:
> On Fri February 6 2004 12:03, Martijn Klingens wrote:
> > On Thursday 05 February 2004 15:54, Waldo Bastian wrote:
> > > I'm not in favor of too much revamping for KDE 4.0 because that tends
> > > to give application developers only more work to do without getting
> > > much in return. It will take longer for development books to catch up,
> > > etc. etc. Having to make changes for Qt4 sounds already bad enough.
> >
> > On the other hand, carrying along bad API for a prolonged timeframe will
> > hurt us just as well. I think we shouldn't refrain from refactoring known
> > weak spots (e.g. stuff already marked deprecated). We should just not
> > refactor for the sake of refactoring...
>
> So then the question becomes which API parts are so bad that they cause
> real hurt?

So it not gets forgotten:

The two KUser classes needs to be merged, perhaps it can be done satisfactory 
without breaking BC.

Cheers,

		Frans