Boost mailing page: Re: [boost] [thread] Expected behaviour of condition variable wait when the mutex is not locked

Date view	Thread view	Subject view	Author view

From: Frank Mori Hess (frank.hess_at_[hidden])
Date: 2008-05-08 09:54:33

Next message: Peter Dimov: "Re: [boost] [thread] Expected behaviour of condition variable waitwhen the mutex is not locked"
Previous message: Peter Dimov: "Re: [boost] Review Request: future library (N2561/Williams version)"
In reply to: Anthony Williams: "Re: [boost] [thread] Expected behaviour of condition variable wait when the mutex is not locked"
Next in thread: Peter Dimov: "Re: [boost] [thread] Expected behaviour of condition variable waitwhen the mutex is not locked"
Reply: Peter Dimov: "Re: [boost] [thread] Expected behaviour of condition variable waitwhen the mutex is not locked"
Reply: Anthony Williams: "Re: [boost] [thread] Expected behaviour of condition variable wait when the mutex is not locked"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 08 May 2008 04:51 am, Anthony Williams wrote:
> To this end, unique_lock is default-constructible and movable, and supports
> lock and unlock operations.

Since when is unique_lock default-constructible? You just mean it has a
defer_lock_t constructor, right?

- --
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIIwYZ5vihyNWuA4URAhxKAJ42W5QM1BOKvMIXslK59Enohu+QagCeLVVR
PMkg5+0sUrPgYXF5TOajC2w=
=RjpP
-----END PGP SIGNATURE-----

Date view	Thread view	Subject view	Author view