changes in ThreadWeaver signals and slots

[Andreas Pakulat]

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).

Andreas

-- 
You can do very well in speculation where land or anything to do with dirt
is concerned.