[Boost-users] [boost.threads] condition api question

I'm curious why the boost::condition class requires a seperate mutex object to be created, and a corresponding scoped lock argument passed to the wait functions. Wouldn't it be easier to just keep a mutex inside the condition object and automatically lock it at the beginning of the wait functions? What am I missing here? -- Frank