Adding ThreadWeaver libraries to kdelibs

[Aaron J. Seigo]

On Thursday 07 September 2006 8:31, Adam Treat wrote:
> I haven't seen a single person say, "No, no, this doesn't belong in
> kdelibs" so I think you should just move it in.  All of these API
> criticisms aside, kdelibs is far from perfect, so requiring threadweaver to
> be perfect in order to move it in is a bit silly.  The API changes can be
> done in kdelibs if need be as there is still plenty of time to make those
> changes.

yes, i think consensus is that it should go in. having API review before hand 
is a good thing, though. it gives us a period of time where people stare at 
new API, which often doesn't happen after the face; this is all in the hopes 
that if we pay a bit of attention to these things the quality of kdelibs will 
increase.

> As for lowercase.cpp VS CamelCase.cpp ... this is not germane to the topic.
> Can we move that to kde-devel where it can be safely ignored?

consistency would be nice. and not too much to ask for.

-- 
Aaron J. Seigo
Undulate Your Wantonness
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060907/afa2b695/attachment.sig>