- Boost-users - lists.boost.org

Problem with bundled BGL properties
by alev mutlu 21 Oct '14

21 Oct '14

Hi all, I am new to BGL and the followings are snippets from my code. When I compile my code I get the following error. Any suggestions, error: no match for ‘operator=’ in ‘city_name.boost::vec_adj_list_vertex_property_map<Graph, GraphPtr, ValueType, Reference, Tag>::operator[] [with Graph = boost::adjacency_list<boost::vecS, boost::vecS, boost::directedS, relation, boost::property<boost::edge_name_t, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::no_property>, boost::no_property, boost::listS>, GraphPtr = boost::adjacency_list<boost::vecS, boost::vecS, boost::directedS, relation, boost::property<boost::edge_name_t, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::no_property>, boost::no_property, boost::listS>*, ValueType = boost::detail::error_property_not_found, Reference = boost::detail::error_property_not_found&, Tag = boost::vertex_name_t](v1) = r’ /home1/mutlu/boost/include/boost-1_37/boost/pending/detail/property.hpp:21: note: candidates are: boost::detail::error_property_not_found& boost::detail::error_property_not_found::operator=(const boost::detail::error_property_not_found&) struct argument{ int is_variable; string value; }; struct relation{ string relation_name; vector<argument> arguments; }; typedef property<edge_name_t, std::string> EdgeNameProperty; typedef adjacency_list<vecS, vecS, directedS, relation, EdgeNameProperty> Graph; int main(){ Graph g; property_map<Graph, vertex_name_t>::type city_name = get(vertex_name, g); property_map<Graph, edge_name_t>::type edge_value = get(edge_name, g); typedef graph_traits<Graph>::vertex_descriptor Vertex; typedef graph_traits<Graph>::edge_descriptor Edge; Vertex v1; v1 = add_vertex(g); city_name[v1]= r; } error: no match for ‘operator=’ in ‘city_name.boost::vec_adj_list_vertex_property_map<Graph, GraphPtr, ValueType, Reference, Tag>::operator[] [with Graph = boost::adjacency_list<boost::vecS, boost::vecS, boost::directedS, relation, boost::property<boost::edge_name_t, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::no_property>, boost::no_property, boost::listS>, GraphPtr = boost::adjacency_list<boost::vecS, boost::vecS, boost::directedS, relation, boost::property<boost::edge_name_t, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::no_property>, boost::no_property, boost::listS>*, ValueType = boost::detail::error_property_not_found, Reference = boost::detail::error_property_not_found&, Tag = boost::vertex_name_t](v1) = r’ /home1/mutlu/boost/include/boost-1_37/boost/pending/detail/property.hpp:21: note: candidates are: boost::detail::error_property_not_found& boost::detail::error_property_not_found::operator=(const boost::detail::error_property_not_found&)

1 0

1.57.0 beta 1 release candidates available for testing
by Marshall Clow 21 Oct '14

21 Oct '14

Release candidate files for 1.57.0 beta 1 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: MD5 (boost_1_57_0_b1_rc1.7z) = 8633fbf5ebb7eaabcb0f309c14646ae3 MD5 (boost_1_57_0_b1_rc1.tar.bz2) = 8e76f98146793f0fbd2492a9151c405b MD5 (boost_1_57_0_b1_rc1.tar.gz) = d41ff3ffb36ac84ff5bf34f799308907 MD5 (boost_1_57_0_b1_rc1.zip) = 8a844dc36284247b2e936f2120e118b2 Thanks! -- The release managers

7 17

1.57.0 beta 1 is now available
by Marshall Clow 20 Oct '14

20 Oct '14

Boost release 1.57.0 beta 1 is now available from SourceForge See http://sourceforge.net/projects/boost/files/boost-binaries/1.57.0.beta.1/ This release contains no new libraries. For details of what's in the release, see http://www.boost.org/users/history/version_1_57_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team P.S. There are a couple of known problems with this beta: * There are problems building with MSVC 8.0 * There are some problems with range/detail/any_iterator.hpp. These will be fixed before the release.

1 0

Boost 1.56 with QT creator, “LNK1104: cannot open file 'libboost_unit_test_framework-vc100-mt-gd-1_56.lib'”
by Kavita 20 Oct '14

20 Oct '14

Hello, I am working on a project of boost unit testing framework using QT creator. I have written a small test program and trying to link "libboost_unit_test_framework-vc100-mt-gd-1_56.lib". This library is present at specified path. But program fails to compile giving said linking error. I searched on net and found that, error should go with "#define BOOST_ALL_NO_LIB". But then, I am getting below error: main.obj:-1: error: LNK2019: unresolved external symbol "class boost::unit_test::test_suite * __cdecl init_unit_test_suite(int,char * * const)" (?init_unit_test_suite@@YAPAVtest_suite@unit_test@boost@@HQAPAD@Z) referenced in function _main The above function is a part of "libboost_unit_test_framework-vc100-mt-gd-1_56.lib". I have written same unit tests using VS 2010 and with the same boost libraries. The program worked properly with expected behavior. What could be possibly going wrong with the usage of boost on QT ? Please help ! -Thanks

6 6

[Log] Writing empty messages with the attributes as the actual payload
by Scott Mueller 17 Oct '14

17 Oct '14

Hello Boost.Users! I'm trying to integrate Boost logging with an existing message infrastructure. In this infrastructure, I have an existing schema that looks like this: Severity Timestamp Process source (much like "channel") Process component (more like a "sub-channel") Message ID A vector of arguments The message is rendered by looking up the message ID to receive the following information: formatting string ("This is an example of %1 message type. The arguments can look like this %4, 3, 2"), the expected argument types which are potentially convertible if the underlying type is different, and so on. I guess what I'm asking is whether or not a logging source can accept the arguments as defined by a compile-time defined schema in the form of attributes with an empty message. Can the logging core route message records defined in this way properly? Is such a thing supported? I'm in the process of writing something up to do this, but I'd like to know in advance whether or not "empty" messages with a bunch of attributes set can get routed to supported sinks. Thanks in advance for your help! Best regards, M. Scott Mueller

1 0

boost serialisation 1.56, why does library version change, when no change in library ?
by avib369 . 16 Oct '14

16 Oct '14

At boost 1.53 the library version was 10, however at boost 1.56 it has jumped to 11. I have not seen any documentation/release notes about boost serialisation changes. What has changed in boost serialisation to merit this change ? The documentation in $BOOST_ROOT/libs/serialization/basic_archive.cpp describes the changes to boost library version, however it does *not* describe why it jumped from 10 -> 11. Any help appreciated. Ta, Avi

2 1

[thread] linux.hpp, BOOST_HAS_PTHREAD_YIELD, BOOST_HAS_SCHED_YIELD
by Rob Conde 16 Oct '14

16 Oct '14

Using boost 1.55, Ubuntu 12.04, gcc 4.6 I'm building boost on linux using the lsb sdk. I was getting the failure (paraphrased): pthread_yield not declared in libs/thread/src/thread.cpp 513 The documentation for pthread_yield (http://man7.org/linux/man-pages/man3/pthread_yield.3.html) says: This call is nonstandard, but present on several other systems. Use the standardized sched_yield(2)<http://man7.org/linux/man-pages/man2/sched_yield.2.html> instead. If I change boost/config/platform/linux.hpp to define BOOST_HAS_SCHED_YIELD instead of BOOST_HAS_PTHREAD_YIELD Then sched_yield is used instead and the build finishes properly. I'm posting this for two reasons: 1. To help others running into the same issue 2. To question whether linux.hpp should be updated officially as I did above 3. If not, why Thanks, Rob Conde

1 0

Boost.Python: Polymorphism downcasting
by Christoff Kok 16 Oct '14

16 Oct '14

Hi, I have a list of base classes in C++, I want to access them in Python as a list of their derived most classes. Is there a build in means to cater for this in Boost.Python? I've made an example the problem I ma facing: // ------------------------------- Code ----------------------------------// #include<memory> #include<iostream> #include<vector> namespace boost { template<class T> T* get_pointer(std::shared_ptr<T>& p){ return p.get(); }} struct Vehicle{ virtual ~Vehicle(){} friend bool operator==(const Vehicle& lhs, const Vehicle& rhs) { return true; }}; struct Boat: public Vehicle{ virtual ~Boat(){} friend bool operator==(const Boat& lhs, const Boat& rhs) { return true; } char const* testBoatSpecificMethod() { return "Floating."; } }; struct Truck: public Vehicle{ virtual ~Truck(){} friend bool operator==(const Truck& lhs, const Truck& rhs) { return true; } char const* testTruckSpecificMethod() { return "Trucking."; } }; class Garage { public: Garage() {}; ~Garage() {}; char const* test() { std::string temp = "Vehicle List Size: " + std::to_string(m_VehicleList.size()); return temp.c_str(); } friend bool operator==(const Garage& lhs, const Garage& rhs) { return true; } std::vector<Vehicle>& vehicleList() { return m_VehicleList; } private: std::vector<Vehicle> m_VehicleList; }; #include <boost/python.hpp> #include <boost/python/suite/indexing/vector_indexing_suite.hpp> BOOST_PYTHON_MODULE(garage_ext) { using namespace boost::python; class_<Garage>("Garage") .def("test", &Garage::test) .def("vehicleList", &Garage::vehicleList, return_internal_reference<1>()); class_<Vehicle,std::shared_ptr<Vehicle>>("Vehicle"); class_<Boat,std::shared_ptr<Boat>,bases<Vehicle>>("Boat") .def("testBoatSpecificMethod", &Boat::testBoatSpecificMethod); class_<Truck,std::shared_ptr<Truck>,bases<Vehicle>>("Truck") .def("testTruckSpecificMethod", &Truck::testTruckSpecificMethod); implicitly_convertible<std::shared_ptr<Boat>,std::shared_ptr<Vehicle>>(); implicitly_convertible<std::shared_ptr<Truck>,std::shared_ptr<Vehicle>>(); class_<std::vector<Vehicle> >("stl_vector_Vehicle") .def(vector_indexing_suite<std::vector<Vehicle> >()); } // --------------------------- Test Script -------------------------------// import garage_ext g = garage_ext.Garage() l = g.vehicleList() l.append(garage_ext.Boat()) print "Expecting a Boat object:" print str(l[0]) print g.vehicleList()[0].testBoatSpecificMethod() garage_ext.f2("Done.") // ------------------------------ Output ---------------------------------// Expecting a Boat object <garage_ext.Vehicle object at 0x7fb17a3bfb50> Traceback (most recent call last): File "test_garage.py", line 7, in <module> print g.vehicleList()[0].testBoatSpecificMethod() AttributeError: *'Vehicle' object has no attribute 'testBoatSpecificMethod'* *'Vehicle' object has no attribute 'testBoatSpecificMethod'* Here I want Vehicle to be a Boat object. If there is not a build in or recommended/known Boost.Python means to handle this problem, I'm thinking of wrapping the list (Lots of accessors to be wrapped in my library.) with a get accessor returning a boost::python::list, storing the derived most types. Getting the derived most type possibly by calling overriden 'getAsDerivedClass' method. I would like to avoid this. I dislike having to add python usage specific methods to the library, for our design and vision values / reasons. Kind Regards, Christoff

1 1

BGL - maximum_adjacency_search - assignedVertices
by Adam Celick 14 Oct '14

14 Oct '14

I was looking at the implementation of maximum_adjacency_search algorithm and got confused by the assignedVertices local variable. It is defined as a set of vertex descriptors and is being iterated over inside the main loop (lines 168-184) but it is never inserted into. So the for loop will always skip. It looks to me as if that part of the code can be eliminated. Am I missing something? Thanks, Adam

1 0

Generating kuratowski subgraph with external edge index map
by Amir Hassan 13 Oct '14

13 Oct '14

Hi! I have a graph which i test for planarity and in case the test fails i want to generate the kuratowski subgraph. I have code that used to compile with boost graph 1.36 but doesn't with 1.56. I guess the problem has to do with the type of the edge index map. you can find code and error messages here: http://stackoverflow.com/questions/26346343/c-boost-graph-generating-kurato… Help is greatly appreciated! greets, amir

1 0