|
From: Frank M. H. <fm...@us...> - 2007-02-20 20:07:18
|
Update of /cvsroot/boost-sandbox/boost-sandbox/libs/signals/doc In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv23886 Modified Files: faq.xml Log Message: Updated faq wrt thread-safety. Index: faq.xml =================================================================== RCS file: /cvsroot/boost-sandbox/boost-sandbox/libs/signals/doc/faq.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- faq.xml 7 Feb 2007 01:21:50 -0000 1.1 +++ faq.xml 20 Feb 2007 20:07:09 -0000 1.2 @@ -3,7 +3,7 @@ "http://www.boost.org/tools/boostbook/dtd/boostbook.dtd"> <section last-revision="$Date$"> <title>Frequently Asked Questions</title> - + <qandaset> <qandaentry> <question> @@ -23,10 +23,9 @@ <para>Is Boost.Signals thread-safe?</para> </question> <answer> - <para>No. Using Boost.Signals in a multithreaded concept is - very dangerous, and it is very likely that the results will be - less than satisfying. Boost.Signals will support thread safety - in the future.</para> + <para>Yes, if the ThreadingModel template parameter of the signal is set to + boost::signals::multi_threaded. If you use thread-safe signals + in your code, you will also have to link to libboost_thread.</para> </answer> </qandaentry> <qandaentry> @@ -71,7 +70,7 @@ ways to do this:</para> <para>The first way involves defining - the <code>BOOST_SIGNALS_NAMESPACE</code> + the <code>BOOST_SIGNALS_NAMESPACE</code> macro to some other identifier (e.g., <code>signalslib</code>) when building and using the Boost.Signals library. Then the namespace of the Boost.Signals library will be |