- Boost-users - lists.boost.org

[geometry] how to using UDT
by Olaf Peter 15 Jun '14

15 Jun '14

Hello, I try to catch some failures using an own user defined type (UDT), but it doesn't compile e.g. it's hardcoded to use std::sqrt: boost_1_55_0/boost/geometry/strategies/cartesian/distance_pythagoras.hpp:165:13: error: no matching function for call to 'sqrt(core::my_type<double>)' further, is there a way to adapt templated points? BOOST_GEOMETRY_REGISTER_POINT_2D(point_type, point_type::coordiante_type, bg::cs::cartesian, x, y) got errrors. Thanks, Olaf

2 2

BGL performance: is pool_allocator possible and does it help iteration performance?
by Jeremy Murphy 14 Jun '14

14 Jun '14

Hi, I'm implementing a graph algorithm that requires a lot of repeated iteration over a graph as it builds it. So I wonder about cache misses. Is it possible to use a pooled allocator with the vector/list that gets used in the VertexList and EdgeList properties of adjacency_list? If there are other techniques for improving search/iteration performance (at the cost of insertion), I'd also be interested. Thanks! Jeremy

1 0

Boost Library Incubator recommended by steering committee
by Beman Dawes 14 Jun '14

14 Jun '14

The Boost Library Incubator (www.blincubator.com) is a web site conceived, designed, and implemented to alleviate the log-jam of libraries waiting to be reviewed by Boost. It helps new library submitters through the process, encourages development of an initial user base, and accumulates feedback in the form of comments, test results and Boost style reviews. The Boost Steering Committee has voted to recommend using the Boost Library Incubator as a prelude to getting a library reviewed by Boost. The Steering Committee recommends libraries currently in the Boost review queue be added to the Incubator by their developers. The relationship between Boost and the Incubator is purely informal, but there as several things Boosters can do to help make the Incubator a success. Authors can submit their libraries and respond to feedback. Users can experiment with submitted libraries and provide feedback on their experience. WordPress/php developers can contribute enhancements to the Boost Library Incubator implementation. The steering committee extends its thanks to Robert Ramey for launching the Boost Library Incubator! --The Boost Steering Committee

3 2

[utility] prior(it, n) for n being an unsigned type
by Adam Romanek 13 Jun '14

13 Jun '14

Hi! I've just finished investigating an issue in my code which led it to an assert/abort in certain cases. It turned out it was caused by the use of boost::prior(it, n) where n was unsigned int with some non-zero value. I found a question [1] on the mailing list back in 2004 which describes this issue. Additionally a solution to this problem was also posted in one of the replies [2]. My question is - why hasn't it made into the repository yet? The current behavior of boost::prior(it, n) when n is unsigned type is far from the one expected by its potential users so I think it should either be properly documented (warned) or fixed immediately. Am I not seeing something? WBR, Adam Romanek [1] http://lists.boost.org/Archives/boost/2004/02/61556.php [2] http://lists.boost.org/Archives/boost/2004/02/61578.php

1 0

std::limits compile errors with boost
by David Frank 13 Jun '14

13 Jun '14

Anyone has seen this?: In file included from ../include/boost/lockfree/detail/freelist.hpp:12, from ../include/boost/lockfree/queue.hpp:24, from test.cpp:2: /usr/local/powerpc-linux-gnu/include/c++/4.3.2/limits:287:22: error: macro "min" requires 2 arguments, but only 1 given Thanks

4 3

<boost::wave> Memory issue when using wave to run a file parser service
by Yong Huang 12 Jun '14

12 Jun '14

Hi all, I run into a memory issue when uses boost wave library. My application runs as a *service *that parses c files. In each individual run, it calls in the wave library through a sub-function call to process one file. I noticed that some memory is not released from wave after each run. The consequence is that the memory usage of the application keeps increasing till the system breaks down. I could reproduce the problem with a simple modification of the quick_start sample code shipped with the boost wave library. (attached below). My system is win64 and I see the problem with both 1.49 and 1.55. (built with b2 toolset=msvc-11.0 address-model=64 --build-type=complete) Something I found during the investigation: * The problem is gone if I build the application with link<static>. (Unfortunately, this is not an option for me) * From the memory usage pattern, it seems that there is a memory pool in place that should have been released after each turn. When repeatedly passing a 4MB file, the memory usage (taken from task maneger) is: 99,700K, 198,404K, 395,404K, 395408K, and 789,396K. When running with static link, the memory usage after each run is: 1800K, 2480K, 2480K, .... The maximum usage is 8300K. Is there any workaround with the problem? Thanks, Yong ------------------------------------- begin of the code --------------------------------------------------- #define BOOST_WAVE_SERIALIZATION 0 // enable serialization #define BOOST_WAVE_BINARY_SERIALIZATION 0 // use binary archives #define BOOST_WAVE_XML_SERIALIZATION 1 // use XML archives /////////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////////// // Include Wave itself #include <boost/wave.hpp> /////////////////////////////////////////////////////////////////////////////// // Include the lexer stuff #include <boost/wave/cpplexer/cpp_lex_token.hpp> // token class #include <boost/wave/cpplexer/cpp_lex_iterator.hpp> // lexer class // sub-function that calls into wave int do_it(std::string filename) { boost::wave::util::file_position_type current_position; std::ifstream instream(filename); std::string instring; instream.unsetf(std::ios::skipws); instring = std::string(std::istreambuf_iterator<char>(instream.rdbuf()), std::istreambuf_iterator<char>()); typedef boost::wave::cpplexer::lex_token<> token_type; typedef boost::wave::cpplexer::lex_iterator<token_type> lex_iterator_type; typedef boost::wave::context<std::string::iterator, lex_iterator_type> context_type; typedef boost::wave::cpplexer::lex_token<> TokenType; typedef boost::wave::cpplexer::lex_iterator<TokenType> LexIterator; LexIterator aIter(instring.begin(), instring.end(), TokenType::position_type( filename.c_str()), boost::wave::language_support( boost::wave::support_cpp | boost::wave::support_option_long_long ) ); LexIterator endIter; for (; aIter != endIter; ) { (*aIter).get_value(); ++aIter; } return 0; } int main(int argc, char *argv[]) { int aNum = 1; for (;;) { do_it("c:\\memleak.txt"); std::cout << "Process the file again (0/1)? \n"; scanf("%d", &aNum); if (aNum == 0) { printf("\nYou entered zero so we stop!\n"); return 0; } } return 0; }

2 1

[python] TypeError when left side is noncopyable
by Igor R 12 Jun '14

12 Jun '14

I'm trying to expose an operator: struct my_class : boost::noncopyable {}; my_class &operator <<(my_class &e, int i); // in the module definition: class_<my_class, boost::noncopyable>("my_class") .def(self << int()) ; However, an attempt to invoke this operator in python causes the following error: TypeError: No to_python (by-value) converter found for C++ type: my_class I guess this is related to the fact my_class is noncopyable, isn't it? Is there a workaround for this issue? Thanks.

1 0

Meeting C++ Schedule released
by Jens Weller 12 Jun '14

12 Jun '14

Hello C++ & Boost Community, since last week the schedule for Meeting C++ is released: http://meetingcpp.com/index.php/schedule14.html Like last year Meeting C++ will feature 21 Talks in 3 Tracks, the conference will be opened by Scott Meyers, the closing Keynote will be given by Hartmut Kaiser. This years Theme Track is "Scientific Programming with C++". Also, if your are a student, you have the chance to participate in our student program which will give 50 Students access to the conference: http://meetingcpp.com/index.php/newsreader/items/meeting-cpp-2014-the-stude… kind regards, Jens Weller

1 0

pure virtuals on multiple hierarchy levels
by Igor R 12 Jun '14

12 Jun '14

Hello, What's the right way to wrap the following, when exposing this hierarchy to Python: sturct base { virtual void func1() = 0; }; struct intermediate : base { virtual void func2() = 0; }; struct derived : intermediate { void func1(); void func2(); }; Thanks.

1 0

[BGL]
by Pablo Madoery 11 Jun '14

11 Jun '14

Hello, I Have 2 graphs: graph1 and graph2, and two sets of edge descriptors. One set is associated to edges of graph1 and another set associated to edges of graph2. I don't understand why is it possible to access information about edges of graph2 by using graph1 and the edge descriptors of graph2. I realized of that because of an own mistake when using graphs. What I would like to know is why is that possible to do and if it should be an exception that can handle this situation. I send the code I was using to test this: #include <iostream> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/graphviz.hpp> #include <fstream> #include "GraphInfo.h" using namespace std; using namespace boost; typedef adjacency_list<setS, vecS, bidirectionalS, VertexInfo, EdgeInfo> Graph; void printGraph(Graph graph, string file) { ofstream ofs(file.c_str()); dynamic_properties dp; dp.property("node_id", get(vertex_index, graph)); dp.property("label", get(&EdgeInfo::weight, graph)); write_graphviz_dp(ofs, graph, dp); } int main() { Graph graph1; Graph::vertex_descriptor a1 = add_vertex(graph1); Graph::vertex_descriptor b1 = add_vertex(graph1); Graph::vertex_descriptor c1 = add_vertex(graph1); Graph::edge_descriptor e1 = (add_edge(a1, b1, graph1)).first; Graph::edge_descriptor e2 = (add_edge(b1, a1, graph1)).first; graph1[a1].id = 10; graph1[b1].id = 20; graph1[c1].id = 30; graph1[e1].weight = 1; graph1[e2].weight = 2; Graph graph2; Graph::vertex_descriptor a2 = add_vertex(graph2); Graph::vertex_descriptor b2 = add_vertex(graph2); Graph::vertex_descriptor c2 = add_vertex(graph2); Graph::vertex_descriptor d2 = add_vertex(graph2); Graph::edge_descriptor e4 = (add_edge(c2, b2, graph2)).first; Graph::edge_descriptor e5 = (add_edge(b2, c2, graph2)).first; Graph::edge_descriptor e6 = (add_edge(d2, a2, graph2)).first; Graph::edge_descriptor e7 = (add_edge(a2, d2, graph2)).first; graph2[a2].id = 10; graph2[b2].id = 20; graph2[c2].id = 30; graph2[e4].weight = 13; graph2[e5].weight = 14; graph2[e6].weight = 15; graph2[e7].weight = 16; // WHY IS THIS POSSIBLE TO DO // IT IS ASKING FOR AN EDGE OF GRAPH2 BUT USING GRAPH1 ??? double weight = graph1[e7].weight; cout<<"weight: "<<weight<<endl; printGraph(graph1, "graph1.dot"); printGraph(graph2, "graph2.dot"); cout << "end" << endl; return 0; } Thank you very much

2 1