On Sat, 2010-01-09 at 11:44 -0500, Scott Lawrence wrote:
> {
> ... code-a ...
> {
> OsLock critical(mutex);
>
> ... code-b ...
> }
> ... code-c ...
> }
>
> the inner set of {} become a nice syntactic part of the lock. I know
> unambiguously that regardless of how complex it becomes, code-b is all
> in the critical region and protected, and neither code-a nor code-c can
> be. What you're suggesting preserves the latter, but not the former.
I've reverted OsLock to its former behavior, i.e., it can't be unlocked.
If one wants to use OsUnLock, one has to take the lock using
OsLockUnlockable. Thus, that latter class is a warning that OsUnLock is
in the offing.
Dale
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
