Re: [boost] [thread] Interest in a locking pointer and lockable concept

From: Frank Mori Hess (frank.hess_at_[hidden])
Date: 2008-03-24 11:49:27

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

On Monday 24 March 2008 11:27 am, Phil Endecott wrote:
> My point is that start_updater does keep a copy of the reference; from
> my original post:
>
> void start_updater(mutex& m, int& val)
> {
>    // spawn a thread that periodically locks m and changes val
> }

Ah, sorry I missed that.  But the poet::monitor_ptr constructed from a 
poet::monitor idea I mentioned would appear to cover your use case?  On the 
other hand, if you're not concerned about shared ownership, I'm not clear on 
what the advantage of passing a LockableRef would be over just passing a 
plain reference to a Lockable?

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

iD8DBQFH582I5vihyNWuA4URAqNoAJ9FIasidhIOKNjqYkKRZSfPgjy2nQCgp+TQ
3Hn1z6fDRtv00o0bu+CQYyM=
=SZHZ
-----END PGP SIGNATURE-----