- Boost-users - lists.boost.org

Never mind ...
by Eric Fowler 12 May '10

12 May '10

bool b_eric_is_a_numnut; MYEDGEPROPS my_edge_props( param ); tie(e01, b_eric_is_a_numnut) = add_edge(v0, v1, my_edge_props, my_graph); All I needed. It was the return, not the parameter. Thanks. Eric

1 0

Problems compiling with bundled properties and add_edge()
by Eric Fowler 12 May '10

12 May '10

I am using bundled properties: typedef unsigned position_type; template<typename T> class POS { public: ... }; template<typename T> struct LEN { T len_sq; }; typedef POS<position_type> POSITION; typedef LEN<position_type> LENGTH; typedef adjacency_list<vecS, vecS, bidirectionalS, POSITION, LENGTH> DG; typedef graph_traits<DG>::vertex_descriptor Vertex; typedef graph_traits<DG>::edge_descriptor Edge; ...and I am calling add_edge() like this [from within the graph class so (*this) resolves to the graph object]: LENGTH l; l.len_sq = whatever; e01 = add_edge(v0, v1, l, *this); The g++ compiler is punishing me with huge error reports that say: ../main.cpp: In constructor ‘DelaunayGraph<T>::DelaunayGraph(const int&, const int&) [with T = unsigned int]’: ../main.cpp:126: instantiated from here ../main.cpp:101: error: no match for ‘operator=’ in ‘((DelaunayGraph<unsigned int>*)this)->DelaunayGraph<unsigned int>::e01 = boost::add_edge [with Graph = boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, POS<unsigned int>, LEN<unsigned int>, boost::no_property, boost::listS>, Config = boost::detail::adj_list_gen<boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, POS<unsigned int>, LEN<unsigned int>, boost::no_property, boost::listS>, boost::vecS, boost::vecS, boost::bidirectionalS, boost::property<boost::vertex_bundle_t, POS<unsigned int>, boost::no_property>, boost::property<boost::edge_bundle_t, LEN<unsigned int>, boost::no_property>, boost::no_property, boost::listS>::config, Base = boost::bidirectional_graph_helper_with_property<boost::detail::adj_list_gen<boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, POS<unsigned int>, LEN<unsigned int>, boost::no_property, boost::listS>, boost::vecS, boost::vecS, boost::bidirectionalS, boost::property<boost::vertex_bundle_t, POS<unsigned int>, boost::no_property>, boost::property<boost::edge_bundle_t, LEN<unsigned int>, boost::no_property>, boost::no_property, boost::listS>::config>](((DelaunayGraph<unsigned int>*)this)->DelaunayGraph<unsigned int>::v0, ((DelaunayGraph<unsigned int>*)this)->DelaunayGraph<unsigned int>::v1, ((const boost::property<boost::edge_bundle_t, LEN<unsigned int>, boost::no_property>&)(& boost::property<boost::edge_bundle_t, LEN<unsigned int>, boost::no_property>(((const LEN<unsigned int>&)((const LEN<unsigned int>*)(& l)))))), ((boost::vec_adj_list_impl<boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, POS<unsigned int>, LEN<unsigned int>, boost::no_property, boost::listS>, boost::detail::adj_list_gen<boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, POS<unsigned int>, LEN<unsigned int>, boost::no_property, boost::listS>, boost::vecS, boost::vecS, boost::bidirectionalS, boost::property<boost::vertex_bundle_t, POS<unsigned int>, boost::no_property>, boost::property<boost::edge_bundle_t, LEN<unsigned int>, boost::no_property>, boost::no_property, boost::listS>::config, boost::bidirectional_graph_helper_with_property<boost::detail::adj_list_gen<boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, POS<unsigned int>, LEN<unsigned int>, boost::no_property, boost::listS>, boost::vecS, boost::vecS, boost::bidirectionalS, boost::property<boost::vertex_bundle_t, POS<unsigned int>, boost::no_property>, boost::property<boost::edge_bundle_t, LEN<unsigned int>, boost::no_property>, boost::no_property, boost::listS>::config> >&)(&((DelaunayGraph<unsigned int>*)this)->DelaunayGraph<unsigned int>::<anonymous>.boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, POS<unsigned int>, LEN<unsigned int>, boost::no_property, boost::listS>::<anonymous>)))’ /usr/include/boost/graph/detail/edge.hpp:35: note: candidates are: boost::detail::edge_desc_impl<boost::bidirectional_tag, unsigned int>& boost::detail::edge_desc_impl<boost::bidirectional_tag, unsigned int>::operator=(const boost::detail::edge_desc_impl<boost::bidirectional_tag, unsigned int>&) make: *** [main.o] Error 1 Yow. It doesn't like the LENGTH param. What can I do? I tried adding an assignment operator and copy constructor, no go. What am I doing wrong? Eric

1 0

[MultiIndex] Visual C++ 10 issue
by Jeremiah Willcock 11 May '10

11 May '10

Are there known problems with MultiIndex on the current VC++ 10 beta? I'm looking in particular at <URL:http://tinyurl.com/39bmudo>. The area around the line VC++ 10 has a problem with (line 276 of distributed_property_map.hpp, the error is on the &std::pair line) is: typedef multi_index::multi_index_container< std::pair<key_type, value_type>, multi_index::indexed_by< multi_index::sequenced<>, multi_index::hashed_unique< multi_index::member<std::pair<key_type, value_type>, key_type, &std::pair<key_type, value_type>::first> > > > ghost_cells_type; and the main error is (full instantiation stack in the link above): D:\boost-test\boost\boost/property_map/parallel/distributed_property_map.hpp(276) : error C2440: 'specialization' : cannot convert from 'boost::detail::parallel::global_descriptor<LocalDescriptor> std::_Pair_base<_Ty1,_Ty2>::* ' to 'boost::detail::parallel::global_descriptor<LocalDescriptor> std::pair<_Ty1,_Ty2>::* ' with [ LocalDescriptor=unsigned int, _Ty1=boost::detail::parallel::global_descriptor<unsigned int>, _Ty2=boost::detail::parallel::global_descriptor<unsigned int> ] Standard conversion from pointer-to-member of base to pointer-to-member of derived is not applied for template arguments What I don't see is where the pointer-to-member of _Pair_base comes from; is that the correct type for the address of a member that's actually from a base class? Or is this a compiler problem? -- Jeremiah Willcock

6 9

[date time] Printing Unix time + microsecond offset
by Hauberg 11 May '10

11 May '10

Hi All (I hope I am posting in the right list; if not please tell me where to go.) I would like to be able to print the current time with microsecond accuracy. I can do that using ptime now = microsec_clock::universal_time (); std::cout << to_iso_extended_string (now) << std::endl; However, I would like to print this information in a different format. Specifically, I would like to print Unix time (i.e. number of seconds since midnight January 1, 1970) followed by the number of microseconds between the current time and the printed Unix time. Any ideas on how to do that? Thanks Søren -- View this message in context: http://old.nabble.com/-date-time--Printing-Unix-time-%2B-microsecond-offset… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

Member function varible callable...
by Etienne Philip Pretorius 11 May '10

11 May '10

Hello List, I know this is probably a stupid question... I have 2 functions like: struct obj { void foo() { }; void bar() { }; } How would I store this in a variable ... so that I can call the function via the variable later... Thank you, Etienne

2 2

[Range] invalid initialization of non-const type with adaptors
by Denis Taniguchi 11 May '10

11 May '10

Hi, I was trying to compile the following simple piece of code: #include <boost/range/algorithm.hpp> #include <boost/range/adaptors.hpp> #include <vector> int main(int argc, char *argv[]) { std::vector<int> vec(10); boost::fill(vec | boost::adaptors::reversed, 1); return 0; } But I get the following erros with gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3: test_fill.cpp: In function ‘int main(int, char**)’: test_fill.cpp:9: error: invalid initialization of non-const reference of type ‘boost::range_detail::reverse_range<std::vector<int, std::allocator<int> > >&’ from a temporary of type ‘boost::range_detail::reverse_range<std::vector<int, std::allocator<int> > >’ /usr/local/include/boost/range/algorithm/fill.hpp:29: error: in passing argument 1 of ‘ForwardRange& boost::range::fill(ForwardRange&, const Value&) [with ForwardRange = boost::range_detail::reverse_range<std::vector<int, std::allocator<int> > >, Value = int]’ Am I missing something here? Best regards, Denis

5 12

Tooltips in the documentation
by Daniel Lidström 11 May '10

11 May '10

Hello, the boost documentation is often excellent. It is very nice to see so many libraries being documented in the same way, which makes it a pleasant reading. However, some of it (generated by Quickbook?) show a tooltip at the cursor location. I find it slightly annoying and not very helpful. Is this choice by design or by accident? Does anyone here find the tooltip useful? Maybe I am the only one slightly annoyed by it? Regards, Daniel Lidström Stockholm, Sweden

6 8

Regression testing of boost libraries
by Yogesh Arora 10 May '10

10 May '10

Hi I am compiling boost 1.39.0 libraires on sun os. I have just started with using boost libraries and dont have much know about them. I read somewhere that after compilation i can run some regression tests to check if everything has compiled properly or not. When i looked at boost regression test webpage it mentioned that it would download the latest boost code and run the test case on it. However i dont want that, I have a copy of boost 1.39.0 which i have compiled on which i want to run these regression test cases. Is there a way to do that. Also someone mentioned that boost maintains a page on which i can check the status of boost unit test on different platforms, but i could not seem to find it. Can someone provide reference to that page. I am especially interested in status of boost libraires on Sun os with toolset=sun Thanks Yogesh

3 5

Re: [Boost-users] [Boost-announce] [1.43.0] Release notice
by Brian Wood 10 May '10

10 May '10

Tom: > I've built windows libraries (vc7.1, vc8, vc9, vc10) off of this, if you > want > them, you can get them from my website: > http://boost.teeks99.com Please don't top post. Brian Wood "The kingdom of heaven is like a treasure hidden in the field, which a man found and hid again; and from joy over it he goes and sells all that he has and buys that field."

1 0

About Using Boost.Python in msvc9 with /MTd and /MT Runtime Libraries
by Isaac Lascasas 10 May '10

10 May '10

After a quick look at the documentation and user list messages I have found that using Boost.Python with msvc MTd or MT Runtime Libraries may have some problems. My first try with Boost.Python gave me this error: c:\work\src\boost_1_43_0\boost/config/auto_link.hpp(297) : fatal error C1189: #error : "Mixing a dll boost library with a static runtime is a really bad idea..." Then I found that it was possible to use the BOOST_PYTHON_STATIC_LIB macro. This worked fine. I am using python 3.1, I have installed both the x86 and x64 python versions in different directories. Can someone explain me why I need to specify this macro and why "Mixing a dll boost library with a static runtime is a really bad idea"? Regards, Isaac Lascasas.

1 0