Re: [Boost-users] [Thread] What do I #include?

From: Khandelwal, Amit (amit.khandelwal_at_[hidden])
Date: 2008-07-11 08:59:38

The way I use mutex is to protect one shared resource. Here is sample
code that I cooked up. I am not sure why you want to use a single mutex
to protect multiple resources. However, if your use case demands it than
wrap those resources in a class and have a mutex as a member variable of
that class.  

HTH.

Call this file let say ThreadSafeQueue.hpp

#include <boost/thread.hpp>
#include <iostream>
#include <queue>
#include <deque>

namespace std {
namespace threadsafe {

template <typename T, typename SEQUENCE = std::deque<T> >
class tsqueue {

    private:
        std::queue<T, SEQUENCE> m_queue;
        boost::mutex mutex;

    public:

        tsqueue() {
        }

        ~tsqueue() {
        }

        void push(const T& x) {
            boost::lock_guard<boost::mutex> lock(mutex);
            m_queue.push(x);
            std::cout << "Push element: " << x << std::endl;
        }

        const T& front() {
            boost::lock_guard<boost::mutex> lock(mutex);
            std::cout << "Pop element: " << m_queue.front() <<
std::endl;
            return m_queue.front();
        }

        void pop() {
            boost::lock_guard<boost::mutex> lock(mutex);
            return m_queue.pop();
        }

        int size() {
            boost::lock_guard<boost::mutex> lock(mutex);
            return m_queue.size();
        }
};

} // namespace threadsafe
} // namespace std

Here is how you can use it.

#include "ThreadSafeQueue.hpp"

int main() {
    std::threadsafe::tsqueue<int> tsf;
    tsf.push(1);
    tsf.front();
    return 0;
}

g++ -Wall -DBOOST_HAS_THREADS  <relevant includes> <relevant library
path> test.cpp -lboost_thread-gcc32-mt 
 

-----Original Message-----
From: boost-users-bounces_at_[hidden]
[mailto:boost-users-bounces_at_[hidden]] On Behalf Of Anthony
Williams
Sent: Friday, July 11, 2008 6:34 AM
To: boost-users_at_[hidden]
Subject: Re: [Boost-users] [Thread] What do I #include?

Adam Nielsen <adam.nielsen_at_[hidden]> writes:

>>> This may seem like a silly question, but is someone able to point me

>>> to where in the Boost docs it tells me which files I need to 
>>> #include to use Boost Threads?
>>
>> It doesn't. Oops. I'll raise a trac issue for it.
>
> Ah, glad it's not me being dumb for once :-)
>
>> You can include <boost/thread.hpp> to get everything.
>
> Does this include shared_mutex?  I was still getting errors about 
> boost::shared_mutex when I included <boost/thread.hpp>, which prompted

> my hunt through the docs in the first place!

It does in the trunk version, but not in 1.35.0

shared_mutex is in <boost/thread/shared_mutex.hpp>

Anthony
-- 
Anthony Williams            | Just Software Solutions Ltd
Custom Software Development | http://www.justsoftwaresolutions.co.uk
Registered in England, Company Number 5478976.
Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL
_______________________________________________
Boost-users mailing list
Boost-users_at_[hidden]
http://lists.boost.org/mailman/listinfo.cgi/boost-users
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above.  If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited.  This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such.  All information is subject to change without notice.
--------
IRS Circular 230 Disclosure:
Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.