current state of KDE_DEPRECATED ?

[Nicolas Goutte]

On Thursday 16 March 2006 22:16, David Faure wrote:
> On Thursday 16 March 2006 10:27, Thiago Macieira wrote:
> > Looks to me like common sense: why keep deprecated methods in KDE 4?
> > The only reason why they'd still be there is compatibility:
>
> Yes, the reason is compatibility, and that's a good enough reason for now,
> IMHO. There's enough work porting away from qt3; porting away from kde3
> just adds to it, so why put even more work on our plate? We can leave it
> for later (when rewriting code we then take the opportunity to fix some
> deprecation warnings) instead of breaking compilation in all kde modules
> for no urgent reason and driving more people away from trunk because it
> doesn't compile...
>
> > >And what about moving deprecated classes to kde3support? I don't know if
> > >I ca do this without breaking a lot of kde programs...
> >
> > KDE3Support is really a big question mark unanswered. Who's going to
> > write it?
>
> kde3support doesn't need to be "written" from scratch, it's mostly classes
> from kde3 ported to KDE4.
>
> > Who's going to maintain it until *at least* KDE 4.2?
>
> The same people who maintained those kde classes in kde3 (yes that means
> nobody for some of them, so what? it was good enough for kde3 ;-)
>
> > Who's going to make sure that its behaviour is the expected behaviour
> > under KDE3?
>
> You mean KDE4.
> Well, I did for some parts of K3ListView, for instance. Anyway a possible
> small bug in K3ListView is _much_ less of a problem than having to rewrite
> all the kde code that uses K3ListView right now !!!

Your position was quite my position... a few weeks ago.

Unfortunately, trying to fix the K3Dock classes has made me think about it and 
I am not sure anymore.

>
(...)

Have a nice day!