[Boost-users] [signals] thread-safe default combiner

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm noticing now that boost::last_value isn't thread-safe when used with a non-void return value, since a thread can't in general be sure the signal will have any slots connected to it when it is invoked. Would it be acceptable to make last_value throw an exception on the non-void, no slots case? Throwing an exception seems preferable to the dreaded "undefined behaviour". Or we could use a slightly modified default combiner with a different name. - -- Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFzKtr5vihyNWuA4URAtTdAKCfJQicTdVtf5qaab5M2PCndy6bowCggwKi DnFSpe3zg5DJsKfCsfnOh7Q= =Tppf -----END PGP SIGNATURE-----