February 2013 - Boost-users - lists.preview.boost.org

Identify cycles in a undirected graph
by NsPx 20 Aug '13

20 Aug '13

Hi all, I use undirected_dfs to detect all cycles in a undirected graph. I detect a cycle with DFSVisitor.back_edge(e,g) but how can I get the list of vertices defining this cycle ? Thanks by advance

4 4

[thread] synchronized_value: value and move semantics
by Vicente J. Botet Escriba 08 Jun '13

08 Jun '13

Hi, boost::synchronized_value (not released yet [1][2][3]) is based on [4]. See below part of this paper adapted to the Boost.Thread interface. Currently boost::synchronized_value is in addition Copyable and Swappable. I was wondering if it is worth adding value and move semantics to synchronized_value. Making it EqualityComparable, LessThanComparable and Movable if the underlying type satisfy these requirements will allow to store them on a Boost.Container/C++11 container. Do you see something completely wrong with this addition? Has some of you had a need for this? Could you share the context? Best, Vicente [1] https://svn.boost.org/svn/boost/trunk/boost/thread/synchronized_value.hpp [2] https://svn.boost.org/svn/boost/trunk/libs/thread/example/synchronized_valu… [3] https://svn.boost.org/svn/boost/trunk/libs/thread/example/synchronized_pers… [4] "Enforcing Correct Mutex Usage with Synchronized Values" by Anthony Williams http://www.drdobbs.com/cpp/enforcing-correct-mutex-usage-with-synch/2252002… ------------- [section The Problem with Mutexes] The key problem with protecting shared data with a mutex is that there is no easy way to associate the mutex with the data. It is thus relatively easy to accidentally write code that fails to lock the right mutex - or even locks the wrong mutex - and the compiler will not help you. std::mutex m1; int value1; std::mutex m2; int value2; int readValue1() { boost::lock_guard<boost::mutex> lk(m1); return value1; } int readValue2() { boost::lock_guard<boost::mutex> lk(m1); // oops: wrong mutex return value2; } Moreover, managing the mutex lock also clutters the source code, making it harder to see what is really going on. The use of synchronized_value solves both these problems - the mutex is intimately tied to the value, so you cannot access it without a lock, and yet access semantics are still straightforward. For simple accesses, synchronized_value behaves like a pointer-to-T; for example: boost::synchronized_value<std::string> value3; std::string readValue3() { return *value3; } void setValue3(std::string const& newVal) { *value3=newVal; } void appendToValue3(std::string const& extra) { value3->append(extra); } Both forms of pointer dereference return a proxy object rather than a real reference, to ensure that the lock on the mutex is held across the assignment or method call, but this is transparent to the user. [endsect] [/The Problem with Mutexes] [section Beyond Simple Accesses] The pointer-like semantics work very well for simple accesses such as assignment and calls to member functions. However, sometimes you need to perform an operation that requires multiple accesses under protection of the same lock, and that's what the synchronize() method provides. By calling synchronize() you obtain an strict_lock_ptr object that holds a lock on the mutex protecting the data, and which can be used to access the protected data. The lock is held until the strict_lock_ptr object is destroyed, so you can safely perform multi-part operations. The strict_lock_ptr object also acts as a pointer-to-T, just like synchronized_value does, but this time the lock is already held. For example, the following function adds a trailing slash to a path held in a synchronized_value. The use of the strict_lock_ptr object ensures that the string hasn't changed in between the query and the update. void addTrailingSlashIfMissing(boost::synchronized_value<std::string> & path) { boost::strict_lock_ptr<std::string> u=path.synchronize(); if(u->empty() || (*u->rbegin()!='/')) { *u+='/'; } } [endsect] [/Beyond Simple Accesses] [section Operations Across Multiple Objects] Though synchronized_value works very well for protecting a single object of type T, nothing that we've seen so far solves the problem of operations that require atomic access to multiple objects unless those objects can be combined within a single structure protected by a single mutex. One way to protect access to two synchronized_value objects is to construct a strict_lock_ptr for each object and use those to access the respective protected values; for instance: synchronized_value<std::queue<MessageType> > q1,q2; void transferMessage() { strict_lock_ptr<std::queue<MessageType> > u1 = q1.synchronize(); strict_lock_ptr<std::queue<MessageType> > u2 = q2.synchronize(); if(!u1->empty()) { u2->push_back(u1->front()); u1->pop_front(); } } This works well in some scenarios, but not all - if the same two objects are updated together in different sections of code then you need to take care to ensure that the strict_lock_ptr objects are constructed in the same sequence in all cases, otherwise you have the potential for deadlock. This is just the same as when acquiring any two mutexes. In order to be able to use the dead-lock free lock algorithms we need to use instead unique_lock_ptr, which is Lockable. synchronized_value<std::queue<MessageType> > q1,q2; void transferMessage() { unique_lock_ptr<std::queue<MessageType> > u1 = q1.unique_synchronize(boost::defer_lock); unique_lock_ptr<std::queue<MessageType> > u2 = q2.unique_synchronize(boost::defer_lock); boost::lock(u1,u2); // dead-lock free algorithm if(!u1->empty()) { u2->push_back(u1->front()); u1->pop_front(); } } [endsect] [/Operations Across Multiple Objects]

2 4

Is boost::this_thread::sleep_for interruption point?
by Serg Gulko 23 May '13

23 May '13

Hello! According to documentation(v 1.50.0) call boost::this_thread::sleep_for can be interrupted. For some reason this functionality not works for me. Here is code sample: //Simple thread function void Test::worker(int delay) { try { boost::this_thread::sleep_for(boost::chrono::milliseconds(delay)); cout << "Doing some work" << endl; } catch (boost::thread_interrupted const& e) { cout << "INTERRUPTED" << endl; } } //Far in the code boost::thread workerThread(boost::bind(&Test::worker, this, 1200)); boost::this_thread::sleep(boost::posix_time::milliseconds(30)); workerThread.interrupt(); boost::this_thread::sleep(boost::posix_time::milliseconds(1500)); I always getting 'Doing some work'... -- View this message in context: http://boost.2283326.n4.nabble.com/Is-boost-this-thread-sleep-for-interrupt… Sent from the Boost - Users mailing list archive at Nabble.com.

3 3

Re: [Boost-users] [CMake] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake.
by Klaim - Joël Lamotte 16 Apr '13

16 Apr '13

Júlio Hoffimann said: > > I don't know if i understood correctly, but you can set the library > directory by hand, please refer to > /usr/share/cmake-<version>/Modules/FindBoost.cmake, in particular the > variable BOOST_LIBRARYDIR. On Thu, Oct 11, 2012 at 1:29 PM, Miller, Frank <FMiller(a)sjm.com> wrote: > A simple solution would be to install only the 64bit version of boost > into a new directory and change the environment variable to point there. > Then FindBoost will only be able to see the version you want. > Thanks, this will solve my immediate problem, but it don't solve it in general. (I will use it though, so thanks) I can't guarantee where the boost libraries are installed, that's why I use FindBoost. My current understanding is that boost don't have a specific default lib dir for different address models, which is the source of the problem as FindBoost script can't rely on a protocol to find these lib files. Am I correct? Joel Lamotte

3 8

[MSM] "favor_compile_time" policy disables "kleene" events. (Bug?)
by Deniz Bahadir 25 Mar '13

25 Mar '13

Hi everyone, Hi Christophe, While trying to speedup compilation of my MSM/eUML-based state machine, I seem to have found a bug. I added the "favor_compile_time" policy to the type-definition of my state-machine as the documentation suggests. I did not use the macro "BOOST_MSM_BACK_GENERATE_PROCESS_EVENT" because I do not have any sub-statemachines. This did speed up compilation, however obviously by changing my transition-table: All "kleene"-events in my transition-table are ignored, when defining the state-machine with the "favor_compile_time" policy. Can anyone confirm this or am I using it wrong? (Was this policy supposed to work with eUML in the first place?) Thanks, Deniz PS: I am using GCC 4.7.2 with Boost 1.53.

3 6

Android: segfault while writing to archive during Serialization
by wespaugh 18 Mar '13

18 Mar '13

Greetings! New to discussion, apologies in advance for any inadvertent misuse of terminology / standards. (also, I tried e-mailing this post directly last night, but it doesn't appear to have shown up, yet. double-apologies if double-post). I'm trying to port my project, which involves some serialization code, to Android. I followed instructions to build boost 1.49 found here: https://github.com/MysticTreeGames/Boost-for-Android and can successfully compile my application using crystax NDK r7 (gcc 4.5.3) , and link it to the Serialization library. Unfortunately! When my application calls the serialization code to send my object to the archive, it crashes. I've reduced my actual code to try and isolate the crash in a way I can post here. std::ofstream outStream(MAP_SAVE_FILE, std::ios_base::binary); boost::archive::text_oarchive outputArchive(outStream, 1); Classroom *c = new Classroom(); CCLog("Outputting archive"); // outputArchive << mapInstance; outputArchive << c; The crash occurs at outputArchive << c; "Fatal signal 11 (SIGEGV) at 0xdeadbaad (code=1), thread 1870 (Thread-97)" which is a segfault, in Androidvania. Ideally I want to be outputting that mapInstance variable that's commented out to archive, but for sanity's sake I made a silly little Classroom class, which I'll include for sanity's sake: class Classroom { friend class boost::serialization::access; template <class Archive> void serialize( Archive &ar, const unsigned int version ) { ar & studentCount; } int studentCount; public: Classroom() { studentCount = 1; } ~Classroom(){} }; I've run across several red flags about wchar support in Android or on gcc versions, so I'm inclined to think that's related. Then again, it appears as though my boost configuration files were aware of the compiler version when it built (that Mystic Tree link at the top really does seem to be on top of things, if anyone's interested), which is how the program was able to compile and run, at all. I'm almost 100% certain this is related to the Android NDK, either the gcc version or the gnu-stl, because I can compile and run this code on Windows through Visual studio with no problem, but it crashes on Android. I've made sure that my app has write permissions to the internal storage being used. I can even write out text files using basic std::ostreams without a crash. I am not at all familiar with dealing with these sorts of compiler- or platform-specific issues; I have a bachelor's in SE which taught me design patterns, architecture, and project management, but nothing like this. I'd greatly appreciate some direction in learning how to work through these kinds of problems, (although I'd even more greatly appreciate an actual solution to the problem I'm seeing). Thanks in advance for any assistance. -- View this message in context: http://boost.2283326.n4.nabble.com/Android-segfault-while-writing-to-archiv… Sent from the Boost - Users mailing list archive at Nabble.com.

2 5

can't get first example in boost tutorial to work
by 7stud 11 Mar '13

11 Mar '13

I'm trying to install boost on mac osx 10.4.7. I followed the tutorial "Getting Started on Unix Variants" found here: http://www.boost.org/doc/libs/1_35_0/ more/getting_started/unix-variants.html Following the instructions in the tutorial, I installed boost in /usr/local as instructed, so my directory structure is: /usr/local/boost_1_34_1/boost But when I run the first example in the tutorial: #include <boost/lambda/lambda.hpp> #include <iostream> #include <iterator> #include <algorithm> int main() { using namespace boost::lambda; typedef std::istream_iterator<int> in; std::for_each(in(std::cin), in(), std::cout << (_1 * 3) << " " ); } I get the error(among others): error: boost/lambda/lambda.hpp: No such file or directory If I change the include path to: #include </user/local/boost_1_34_1/boost/lambda/lambda.hpp> I get the error(among others): error: boost/lambda/core.hpp: No such file or directory But core.hpp is in the lambda directory: /usr/local/boost_1_34_1/boost/lambda$ ls algorithm.hpp control_structures.hpp lambda.hpp bind.hpp core.hpp loops.hpp casts.hpp detail numeric.hpp closures.hpp exceptions.hpp switch.hpp construct.hpp if.hpp I'm using the Xcode 2.4 IDE to run my C++ programs. I also tried to execute the program from the command line with the original include path: #include <boost/lambda/lambda.hpp> but I get the same error: ~/2testing/dir1$ g++ prog1.cpp prog1.cpp:1:35: error: boost/lambda/lambda.hpp: No such file or directory prog1.cpp: In function 'int main()': prog1.cpp:8: error: 'boost' has not been declared prog1.cpp:8: error: expected namespace-name before ';' token prog1.cpp:8: error: '<type error>' is not a namespace prog1.cpp:11: error: '_1' was not declared in this scope I get the same errors again with the full include path: #include </user/local/boost_1_34_1/boost/lambda/lambda.hpp> $ g++ prog1.cpp In file included from prog1.cpp:1: /usr/local/boost_1_34_1/boost/lambda/lambda.hpp:14:33: error: boost/lambda/core.hpp: No such file or directory /usr/local/boost_1_34_1/boost/lambda/lambda.hpp:21:52: error: boost/lambda/detail/operator_actions.hpp: No such file or directory /usr/local/boost_1_34_1/boost/lambda/lambda.hpp:22:61: error: boost/lambda/detail/operator_lambda_func_base.hpp: No such file or directory /usr/local/boost_1_34_1/boost/lambda/lambda.hpp:23:63: error: boost/lambda/detail/operator_return_type_traits.hpp: No such file or directory /usr/local/boost_1_34_1/boost/lambda/lambda.hpp:26:45: error: boost/lambda/detail/operators.hpp: No such file or directory /usr/local/boost_1_34_1/boost/lambda/lambda.hpp:30:46: error: boost/lambda/detail/member_ptr.hpp: No such file or directory prog1.cpp: In function 'int main()': prog1.cpp:8: error: 'boost' has not been declared prog1.cpp:8: error: expected namespace-name before ';' token prog1.cpp:8: error: '<type error>' is not a namespace prog1.cpp:11: error: '_1' was not declared in this scope What path should I be using? Or, should I set an environment variable somewhere?

6 16

[assign] Support for std::array
by Bill Buklis 04 Mar '13

04 Mar '13

For compilers that support it (especially VS2010 or later), is or will there be support for std::array with boost::assign? For example list_of works with boost::array, but not std::array. I'm currently still on boost 1.50. If this has already been added to a post 1.50 build, then awesome. Hopefully, I'll be upgrading soon. Thanks, -- Bill

2 2

Re: [Boost-users] Boost.MSM cc1plus.exe:: error: out of memory allocating 65532
by degoah 04 Mar '13

04 Mar '13

Hi, I'm User using the 32bit version of gcc. The compiled binary has to be used on a 32 bit system. I know, i can pass to gcc the 32 bit flag "-m32".... Regards, R niXman <i.nixman(a)gmail.com> schrieb: 2013/2/26 RaRi: > My system environment is configured as follows: > > Operating system : Windows 7 64-Bit > MinGW32, > gcc v.4.72 You are using 32-bit mingw or 64-bit? Please show the output of 'g++ -v' -- Regards, niXman _____________________________________________ Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingwbuilds/ _____________________________________________ Another online IDE: http://liveworkspace.org/ _____________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

7 27

build error boost 1.53.0
by Dev Guy 04 Mar '13

04 Mar '13

Hello I got the following build errors on my linux box building version 1.53.0 gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/cpplexer/re2clex/aq.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/cpplexer/re2clex/cpp_re.o gcc.archive bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/libboost_wave.a common.copy /home/yadav/dev/cpp/boost_1.53.0/lib/libboost_wave.a ...failed updating 56 targets... ...skipped 6 targets... ...updated 10989 targets... Linux version is: uname -a Linux karma 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux GCC Version gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.7.2-2ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) Thanks!

3 3