I was confusing with the lib I'm used to in which the conditionVar is
given the mutex on construction, and keeps attached to the same one
through its life.
But, this doesn't change the meaning of my question at all. Maybe just
the wording "the lock" to "a lock" or "some lock".
That only means that notify_all must do some locking on the
conditionVar some way, and in any case (even if no threads are
blocked) it will have to perform some atomic operations. What I'm
saying is that I think there should be a version locked_notify_all
that requires the caller to make sure the conditionVar is mutexed (not
being currently used on another thread, except for inside wait*() on
the waiting i.e. with the lock released).
[ See http://www.yqcomputer.com/
[ comp.lang.c++.moderated. First time posters: Do this! ]