Re: Weird problem with mutex and lock error

AFAICT, the recursive locking of the mutex is most definitely "intended";
how else does one explain the following function's:
____________________________________________________________
    bool empty() const
    {
        boost::mutex::scoped_lock lock(the_mutex);
        return the_queue.empty();
    }

    bool try_pop(Data& popped_value)
    {
        boost::mutex::scoped_lock lock(the_mutex);
        if(the_queue.empty())
        {
            return false;
        }

        popped_value=the_queue.front();
        the_queue.pop();
        return true;
    }
____________________________________________________________

AFAICT, `try_pop()' does lock the mutex twice... ;^o