Re: [Boost-users] How to use scoped_lock

The problem is the second argument in the lock construct. The old mechanism of constructing an unlocked lock went away in (I think) boost 1.35. Yeah, I'm using boost 1.40. I don't remember how it gets there, but the I do remember (from cleaning up a bunch of explicit and unnecessary true second arguments in some code I inherited) that the failure was reporting something about timed_mutex.

Thank you very much.