-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 03 February 2007 18:28 pm, Timmo Stange wrote:
I took Boost.Signals, removed grouping, naming and tracking (which are together responsible for more than half of the code) and added rudimentary threading support with a single recursive_mutex. I didn't want to spam the list with several kB of compressed code, so I put it here: http://www.sepulchrum.com/sources/mt_signals.tar.gz
I'm noticing the mutex appears in the precompiled library part of the code. A desirable design goal for the final implementation is for the user to be able to put thread-unsafe signals in his single-threaded code and not have to link to libboost_thread and other threading libraries. It seems like that would either require the mutex code be kept in the headers, in classes templated by the thread-safety policy (probably partial template specializations), or two separate precompiled library provided, one for the thread-safe and one for the thread-unsafe signals. - -- Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFx0jy5vihyNWuA4URAhgxAKDI4WWRts5E6PZ4HnuCkokfo8G7TQCgjBME kTOjhJjMGJ7iYf/RhL4n/As= =IwaO -----END PGP SIGNATURE-----