changes in ThreadWeaver signals and slots
Paulo Moura Guedes
moura at kdewebdev.org
Tue May 15 17:51:45 BST 2007
On Tuesday 15 May 2007 16:03, Andreas Pakulat wrote:
> On 15.05.07 15:09:43, Cyrille Berger wrote:
> > > This is binary compatible,
> > Not really, as any binary build with the old kdelibs won't work with the
> > newer, and further more I also think it breaks API freeze, as it requires
> > a code change in the application.
> > Now it can be argue wether the change was needed or not, but I still
> > believe it should at least have been done on a Monday.
> I agree with Cyrille here, especially as this doesn't give any
> compilation errors. Also I doubt it would've been a real problem to port
> the few places that use ThreadWeaver along with the commit
> (koffice, kdepim, kdewebdev and kdevevelop, according to lxr, 68
> Occurences of the term threadweaver in those modules).
KLinkStatus is already ported which makes it done for kdewebdev.
More information about the kde-core-devel