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

[interprocess] Shared memory object
by Patrick Steele 21 Feb '14

21 Feb '14

Hi, can anyone tell me if there is a performance or other difference between boost::interprocess::shared_memory_object and boost::interprocess::windows_shared_memory? With the version of boost we were using back in 2011 ( boost 1.48 ), we found that windows_shared_memory operated faster than shared_memory_object when transporting around 10MB of data. Is this still the case? Thanks, Patrick

4 5

Gsoc
by Anulesh Tiwari 21 Feb '14

21 Feb '14

I've been looking at the various projects and the previous years project . I came across the boost.ublas project that was offered last year . This project seems very cool . Is the project going to be offered again ? The idea of adding additional protocols or modifying existing protocols sounds fun . There will be very likely a project proposal for the boost.ublas project, content will be very similar :) I would love to get a better feel about the entire boost project . Any pointers on how to do the same would be very helpful.

1 1

Build problems with 64-bit VC12 (MSVS2013)
by Craig Henderson 21 Feb '14

21 Feb '14

Hi all, I am having trouble building Boost 1.55 for x64 using VC12. 32-bit builds without error, but 64-bit fails. All of the errors are boost/archive/iterators/transform_width.hpp(151) : error C2039: 'min' : is not a member of 'std' and repeats a lot I added #include <algorithm> to the beginning of the transform_width.hpp header file, and the build now completes without error. However, my app has two linker errors linking with libboost_system-vc120-mt-1_55.lib features.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::system_category(void)" (?system_category@system@boost@ @YAAEBVerror_category@12@XZ) referenced in function "public: __cdecl boost::system::error_code::error_code(void)" (??0error_code@system@boost@ @QEAA@XZ) features.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::generic_category(void)" (?generic_category@system@boost@ @YAAEBVerror_category@12@XZ) referenced in function "void __cdecl boost::system::`dynamic initializer for 'errno_ecat''(void)" (??__Eerrno_ecat@system@boost@@YAXXZ) Again, the 32 bit builds and links Ok. I'm thinking that as the problematic file in Boost in is an 'archive' directory, perhaps the wrong include file is being picked up? But I can't find the difference in 32/64 configurations to find the cause. Is this a known problem? Any suggestions how to diagnose or (preferably!) fix this? Many thanks Craig

1 0

Where is BOOST_TEST - the universal testing tool
by Adi Shavit 21 Feb '14

21 Feb '14

Hi, I read here<http://boost.2283326.n4.nabble.com/test-BOOST-TEST-universal-testing-tool-t…>and here <http://lists.boost.org/Archives/boost/2013/09/206202.php>about BOOST_TEST - the universal testing tool. Where can I find it? Is it still not part of the library? Thanks, Adi

7 15

template trick
by gast128 20 Feb '14

20 Feb '14

I recently watched Stephen Lavavej's excellent channel9 video 'Core C++, 2 of n' in which he described a nice trick to stop template argument deduction: template <typename T> void (T t1, typename std::identity<T>::type t2) { } Browsing the internet for a similar problem, I recently discovered that Peter Dimov already described this trick in 2002 in 'Template function type inference with references' comp.lang.c++.moderated. Boost is more for the libraries, but could it also reserve some space for documenting these template tricks?

4 3

Should boost libs be rebuilt after applying patch?
by qplace 19 Feb '14

19 Feb '14

boost 1.55 I had to apply the patch defined in Ticket #9369 to the boost source file. I did it after libraries were built. Should I now rebuild the libraries again?

3 5

path of test-binary
by dib 19 Feb '14

19 Feb '14

Hi, how can I get the path where b2 placed the binaries of boost tests? Problem is the following: some of the tests need the path to a shared library, which is built together with the tests. in the lib/mylib/tests/Jamfile.v2 I have the following: [...] # our test lib for shared library tests lib test_library : test_library.cpp ; test-suite mylib : # # shared library # [ run shared_library_load_test.cpp ] [ run shared_library_get_symbol_test.cpp ] # # [...] Inside shared_library_*_test.cpp I need something like this: boost::filesystem::path tstlib("bin.v2/libs/mylib/test/mycompiler/test_library.so"); As boost.build decides by itself where to put the binary, i cannot hardcode the path in the source-files.. Is there a way to get the path from boost.build? If not, how could I solve this problem? -- regards dib

3 2

Unit Tests and function calling
by Charles Yates 19 Feb '14

19 Feb '14

Hi, Just wanted a second opinion on how best to handle calling functions which invoke BOOST_REQUIRE and BOOST_CHECK type logic. For example, if I have a test like: void stuff( ... ) { BOOST_REQUIRE( ... ); BOOST_CHECK( ... ); } BOOST_AUTO_TEST( check_stuff ) { stuff( case1 ); stuff( case2 ); stuff( case3 ); } in the CLF log case at least, I only see which lines in stuff failed, but not which which case. I can change things so that we have: bool stuff( ... ) { bool result = true; if ( ( result = require-predicate ) == true ) result = check-predicate; return result; } BOOST_AUTO_TEST( check_stuff ) { BOOST_CHECK( stuff( case1 ) ); BOOST_CHECK( stuff( case2 ) ); BOOST_CHECK( stuff( case3 ) ); } but then I lose the info in the logs over which predicates are failing and it's generally a bit nasty :). As a result, I've been playing with this which seems to encapsulate things pretty well for me (though may introduce more parenthesis than is strictly necessary and may introduce shadowed variables and other issues?): #define BOOL_CHECK( result, pred ) { bool pred_result; BOOST_CHECK( pred_result = ( pred ) ); result = pred_result && result; } #define BOOL_REQUIRE( pred ) { bool pred_result; BOOST_CHECK( pred_result = ( pred ) ); if ( !pred_result ) return pred_result; } #define BOOL_REQUIRE_EQUAL( name, value ) { bool pred_result; BOOST_CHECK( pred_result = ( ( name ) == ( value ) ) ); if ( !pred_result ) return pred_result; } void stuff( ... ) { bool result = true; BOOL_REQUIRE( ... ); BOOL_CHECK( result, ... ); return result; } BOOST_AUTO_TEST( check_stuff ) { BOOST_CHECK( stuff( case1 ) ); BOOST_CHECK( stuff( case2 ) ); BOOST_CHECK( stuff( case3 ) ); } when one of the predicates fails, I get 2 errors in the log - the first being the specific line in 'stuff' and the second being failing case. I've only tested it with g++ and don't know if it's a sensible approach - wondered if any of you guys had any suggestions? Cheers, Charlie

3 3

[BGL] isomorphism: how to define vertex invariant
by Pablo Madoery 19 Feb '14

19 Feb '14

Hi, I have two graphs and I want to know if they are isomorphic. I adjunct the graphs in .png. I read the documentation but i can't figure out how i must define the vertex invariant correctly. what I want is to consider that two graph are not isomorphic taking count of the vertices ids (the unsigned int value that they have). In the example i give I want the function isomorphism to return false. actually it return true. Thank you ! //////////////////////////////////////////////////////////////////////////////////////////// Graph graph1; Graph::vertex_descriptor aA = add_vertex(graph1); Graph::vertex_descriptor bA = add_vertex(graph1); Graph::vertex_descriptor cA = add_vertex(graph1); Graph::edge_descriptor edA1 = (add_edge(aA, bA, graph1)).first; Graph::edge_descriptor edA2 = (add_edge(bA, cA, graph1)).first; graph1[edA1].weight = 1; graph1[edA2].weight = 2; //////////////////////////////////////////////////////////////////////////////////////////// Graph graph2; Graph::vertex_descriptor aB = add_vertex(graph2); Graph::vertex_descriptor bB = add_vertex(graph2); Graph::vertex_descriptor cB = add_vertex(graph2); Graph::edge_descriptor edB1 = (add_edge(bB, aB, graph2)).first; Graph::edge_descriptor edB2 = (add_edge(aB, cB, graph2)).first; graph2[edB1].weight = 1; graph2[edB2].weight = 2; /////////////////////////////////////////////////////////////////////////////////////////// bool isIso = boost::isomorphism(graph1, graph2);

1 0

Meeting C++ 2014 - Call for Papers
by Jens Weller 19 Feb '14

19 Feb '14

Hello boost community, Meeting C++ 2014 has been announced today, it will be in Berlin on the 5th and 6th December! More details on the conference in the official announcement: http://meetingcpp.com/index.php/newsreader/items/announcing-meeting-c-2014-… With the announcement, also the call for paper is now again open till April 20th. This years theme track of the conference is "Scientific Programming with C++". I'm looking for a diverse set of talks about C++, talks about boost, Qt, STL, any libraries, testing, the C++ language (C++11/14/1y) or any other C++ related topic. More details on the call for papers: http://meetingcpp.com/index.php/newsreader/items/call-for-papers-meeting-c-… Kind regards, Jens Weller

1 0