- Boost-users - lists.boost.org

Re: [Boost-users] Boost.Asio, An invalid argument was supplied.
by stefys 24 Nov '08

24 Nov '08

You were right, my apologies. Apparently, the problem was lying in preparing the acceptor to wait for clients. I was doing .bind() on it, but I was forgetting to do .listen(). Best regards, Steven

2 1

[multiindex] Why not to add B+Tree index to multiIndex?
by fgmailbox 24 Nov '08

24 Nov '08

we can use multiindex as a memory db,but the multiindex only support hash index and Order index(RB TREE),why not to add b+ Tree Index to multiindex to make it much faster . 2008-11-20 fgmailbox

5 5

[Preprocessor] Auitomatic switch generation for template class instanciation
by Olivier Tournaire 24 Nov '08

24 Nov '08

Hi all, I am currently completly lost with boost::preprocessor. I am trying to automatically generate a switch ... case structure with this lib and I cannot figure how I can do what I want. Here is the problem. I have a class templated over 2 parameters (in reality, more ...). At run time, I need to choose a specific instanciation for a user given values. An example : class MyDataEnergy { // ... }; class AnotherDataEnergy { // ... }; class MyPriorEnergy { // ... }; class AnotherPriorEnergy { // ... }; template <typename DataEnergyType , typename PriorEnergyType> class MyModel : public DataEnergyType , public PriorEnergyType { // ... }; Now, somewhere in the code, a user specifies which energies to use, and I have to instanciate MyModel with those energies: // ... int priorType = ValueComingFromSomewhere(); int dataType = AnotherValueComingFromSomewhere(); switch(priorType) { case 0: switch(dataType) { case 0: { MyModel<MyPriorEnergy,MyDataEnergy> aModel; aModel.SetInput(...); aModel.Optimize(...); } break; case 1: { MyModel<MyPriorEnergy,AnotherDataEnergy> aModel; aModel.SetInput(...); aModel.Optimize(...); } break; default: break; } case 1: switch(dataType) { case 0: { MyModel<MyPriorEnergy,MyDataEnergy> aModel; aModel.SetInput(...); aModel.Optimize(...); } break; case 1: { MyModel<MyPriorEnergy,AnotherDataEnergy> aModel; aModel.SetInput(...); aModel.Optimize(...); } break; default: break; } default: break; } I would like to know if there is a way to automate the above switch generation. As I have 5 templates, and not only 2, this will really helps ... I tried using BOOST_PP_SEQ_FOR_EACH but did not came to a result. Then, there is a lot of duplication in the above code. Am I doing the right way ? Hope you could help, Best regards, Olivier -- Dr. Olivier Tournaire Chargé de recherches MATIS - Institut Géographique National 73, Ave de Paris 94165 St Mandé cedex, France tel: (+33) 1 43 98 80 00 - 71 25 fax: (+33) 1 43 98 85 81

2 3

[Proto] POD expression can't be used in std::vector
by Joel Falcou 23 Nov '08

23 Nov '08

I have a expression who use BOOST_PROTO_EXTEND to be used as a POD type and I have a class inheriting from this expression to build a terminal class. When I build a std::vector of this terminal class using vector(size_t n) constructor I got the following error : /usr/include/c++/4.3.2/bits/stl_uninitialized.h:192: erreur: no matching function for call to ‘_Construct(const nt2::cmplx_expr<boost::proto::exprns_::expr<boost::proto::tag::address_of, boost::proto::argsns_::list1<nt2::cmplx_expr<boost::proto::exprns_::expr<boost::proto::tag::terminal, boost::proto::argsns_::term<std::pair<float, float> >, 0l> >&>, 1l> >, const nt2::cmplx<float>&)’ And same for _Destruct() Seems & is used on the expression instead of the terminal class (a bit like the cout bug we found earlier). Is it a proto bug or a std bug ? -- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35

4 14

Re: [Boost-users] [boost] Maintenace Guidelines wiki page
by vicente.botet 23 Nov '08

23 Nov '08

----- Original Message ----- From: "Robert Ramey" <ramey(a)rrsd.com> To: <boost(a)lists.boost.org> Cc: <boost-users(a)lists.boost.org> Sent: Saturday, November 22, 2008 11:28 PM Subject: Re: [boost] [Boost-users] Maintenace Guidelines wiki page > > vicente.botet wrote: >> ----- Original Message ----- >> From: "Robert Ramey" <ramey(a)rrsd.com> >> To: <boost-users(a)lists.boost.org> >> Cc: <boost(a)lists.boost.org> >> Sent: Saturday, November 22, 2008 9:19 PM >> Subject: Re: [Boost-users] Maintenace Guidelines wiki page >> I really think that *we can* achieve this goal. > > I would say 'we COULD' achieve this goal - if there was a > true desire to do so. You don't belive that things COULD change? >>> Your "Maintainence Guidlines" presume a consensus >>> about what should be acceptable practice where no >>> such consensus actually exists. >> >> Which acceptable practice are you referring to for which there is no >> consensus? > > My view is that it is good practice to consider > breaking an interface should be considered a bug. Does your view accepts that exceptionally a well documented breaking change with a reasoable deprecated period could not be considered a bug? > The responses to the posting cited above, indicate > to me that there is no consensus to support > this view point. You are right, there was no consensus at all respect to this point. May be we can reach a consensus in other points that can make Boost more backward compatible if not completly backward compatible. Do you think that the deprecation of a feature should be considered as a bug? If not how long should a reasonable period be for you? <snip> ... >> Please could you participate in the elaboration of this guidelines, > > Basically, the guidelines are fine Thanks. > The guidelines for authors should be separated from those > for users. Yes, I could add an index by author, user, RM. Why not. > For users, "don't use "using" " could be part of a larger list > of suggestions for getting the most benefit from the libraries. I'm sure that you have think about it already. Could you share with us some of these suggestions? Thanks, Vicente

2 4

enable_if on operator type()
by Joel Falcou 23 Nov '08

23 Nov '08

How can I set up SFINAE using enable_if on method like struct foo { template<class T> operator T() { return T(1); } }; I want the operator T() to be ther only if T is arithemtic for example. TIA -- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35

3 3

Boost.Asio, An invalid argument was supplied.
by stefys 23 Nov '08

23 Nov '08

Hello. I am trying to write a simple server, and I am using an asynchronous acceptor to get clients: acceptor.async_accept(crtclient->getSocket(), boost::bind(&Server::gotClient, this, boost::asio::placeholders::error)); As soon as this is executed, my Server::gotClient gets called with ec.message()="An invalid argument was supplied." Apparently the problem is that I am supplying an invalid socket with crtClient->getSocket(), but I can't understand how can this be. crtClient is a boost::shared_ptr<Client>. class Client { ... public: Client (boost::asio::io_service &ioserv, Server &server) : socket_(ioserv), ... {} ... boost::asio::ip::tcp::socket &getSocket () { return socket_; } ... private: boost::asio::ip::tcp::socket socket_; ... }; What could be wrong? Am I constructing socket incorrectly with socket_(ioserv)? Because if I construct it with socket_(ioserv, boost::asio::ip::tcp::v4()), I get the error "Already open" in ec.message(), rather than "An invalid argument was supplied".

2 1

[Property Tree] Compilation issue with Boost 1.37.0 Beta 1 issue
by Johan Råde 23 Nov '08

23 Nov '08

The property tree version in the trunk works with Boost 1.36 but not with 1.37 Beta 1. When I compile the following code istream is; ptree pt; read_xml(is, pt); with MSVS 9.0 I get the following error: 3>C:\Boost\include\boost-1_37\boost/iterator/iterator_adaptor.hpp(230) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' 3> with 3> [ 3> x=false 3> ] 3> C:\Boost\include\boost-1_37\boost/iterator/iterator_adaptor.hpp(335) : see reference to function template instantiation 'void boost::detail::iterator_adaptor_assert_traversal<boost::forward_traversal_tag,boost::random_access_traversal_tag>(void)' being compiled 3> C:\Boost\include\boost-1_37\boost/iterator/iterator_adaptor.hpp(334) : while compiling class template member function 'void boost::iterator_adaptor<Derived,Base,Value,Traversal>::advance(__w64 int)' 3> with 3> [ 3> Derived=boost::spirit::position_iterator<std::_Vector_const_iterator<Ch,std::allocator<char>>>, 3> Base=std::_Vector_const_iterator<Ch,std::allocator<char>>, 3> Value=const char, 3> Traversal=boost::forward_traversal_tag 3> ] 3> C:\Boost\include\boost-1_37\boost/spirit/home/classic/iterator/position_iterator.hpp(156) : see reference to class template instantiation 'boost::iterator_adaptor<Derived,Base,Value,Traversal>' being compiled 3> with 3> [ 3> Derived=boost::spirit::position_iterator<std::_Vector_const_iterator<Ch,std::allocator<char>>>, 3> Base=std::_Vector_const_iterator<Ch,std::allocator<char>>, 3> Value=const char, 3> Traversal=boost::forward_traversal_tag 3> ] 3> C:\Program Files\Boost\Unofficial\boost/property_tree/detail/xml_parser_read_spirit.hpp(709) : see reference to class template instantiation 'boost::spirit::position_iterator<ForwardIteratorT>' being compiled 3> with 3> [ 3> ForwardIteratorT=std::_Vector_const_iterator<Ch,std::allocator<char>> 3> ] 3> C:\Program Files\Boost\Unofficial\boost/property_tree/xml_parser.hpp(45) : see reference to function template instantiation 'void boost::property_tree::xml_parser::read_xml_internal<Ptree>(std::basic_istream<_Elem,_Traits> &,Ptree &,int,const std::string &)' being compiled 3> with 3> [ 3> Ptree=boost::property_tree::ptree, 3> _Elem=char, 3> _Traits=std::char_traits<char> 3> ] 3> .\GeneAuxParser.cpp(33) : see reference to function template instantiation 'void boost::property_tree::xml_parser::read_xml<boost::property_tree::ptree>(std::basic_istream<_Elem,_Traits> &,Ptree &,int)' being compiled 3> with 3> [ 3> _Elem=char, 3> _Traits=std::char_traits<char>, 3> Ptree=boost::property_tree::ptree 3> ] --Johan Råde

2 3

Re: [Boost-users] [boost] Maintenace Guidelines wiki page
by Vicente Botet 23 Nov '08

23 Nov '08

----- Original Message ----- From: "Henrik Sundberg" <storangen(a)gmail.com> To: <boost(a)lists.boost.org> Sent: Sunday, November 23, 2008 3:13 PM Subject: Re: [boost] [Boost-users] Maintenace Guidelines wiki page > > On Sun, Nov 23, 2008 at 2:37 PM, vicente.botet <vicente.botet(a)wanadoo.fr> wrote: >> Do you know if the author can change himself the permision on his own SVN files? > > Subversion is not meant to be used that way, as I understand it. Locks > would give the effect you describe, but they aren't meant to be used > for this. Oh, as a last resort he could change the permission in its own SVN copy. <snip> > I think you say that files that has been copied to tags, shall not be > edited in trunk. That seems like hindering development. I see no real > difference between bugs/changes in test code and bugs/changes in C++ > code. Ok, I see now your concern. Of course if there is a bug on the test file it must be modified, but it is a good practice to let them unchanged when there is no bug in. >> I hope that it is clear that I don't want to impose any rule to the authors, release manager or users. Guidelines that are used could incite other to use them. If some of the guidelines seems no useful at all, I have no problem to remove them from this Maintenance Guidelines. > > I think you're doing a very good thing by writing this guideline. I > believe in guidelines too. I actually believe in some rules as well. Me too.

1 0

Patch for push_relabel_max_flow
by Tim Keitt 23 Nov '08

23 Nov '08

I am working with custom graph classes in the Graph library. These classes construct out edge iterators on the fly. This caused problems with push_relabel_max_flow as it uses repeated calls to out_edges to retrieve the end iterator. I've modified the code to store iterator pairs, rather than repeatedly call out_edges. Here's the diff: 124c124 < current(num_vertices(g_), out_edges(*vertices(g_).first, g_).second), --- > current(num_vertices(g_), out_edges(*vertices(g_).first, g_)), 152c152 < current[u] = out_edges(u, g).first; --- > current[u] = out_edges(u, g); 243c243 < current[v] = out_edges(v, g).first; --- > current[v] = out_edges(v, g); 265c265 < for (ai = current[u], ai_end = out_edges(u, g).second; --- > for (ai = current[u].first, ai_end = current[u].second; 294c294 < current[u] = ai; --- > current[u].first = ai; 353c353 < current[u] = min_edge_iter; --- > current[u].first = min_edge_iter; 447c447 < current[u] = out_edges(u, g).first; --- > current[u] = out_edges(u, g); 458,459c458,459 < for (; current[u] != out_edges(u, g).second; ++current[u]) { < edge_descriptor a = *current[u]; --- > for (; current[u].first != current[u].second; ++current[u].first) { > edge_descriptor a = *current[u].first; 472c472 < delta = min BOOST_PREVENT_MACRO_SUBSTITUTION(delta, residual_capacity[*current[v]]); --- > delta = min BOOST_PREVENT_MACRO_SUBSTITUTION(delta, residual_capacity[*current[v].first]); 476c476 < v = target(*current[v], g); --- > v = target(*current[v].first, g); 481c481 < a = *current[v]; --- > a = *current[v].first; 491,492c491,492 < for (v = target(*current[u], g); v != u; v = target(a, g)){ < a = *current[v]; --- > for (v = target(*current[u].first, g); v != u; v = target(a, g)){ > a = *current[v].first; 495c495 < color[target(*current[v], g)] = ColorTraits::white(); --- > color[target(*current[v].first, g)] = ColorTraits::white(); 502c502 < ++current[u]; --- > ++current[u].first; 509c509 < if (current[u] == out_edges(u, g).second) { --- > if (current[u].first == current[u].second) { 524c524 < ++current[u]; --- > ++current[u].first; 635c635 < std::vector< out_edge_iterator > current; --- > std::vector< std::pair<out_edge_iterator, out_edge_iterator> > current; -- Timothy H. Keitt http://www.keittlab.org/

1 0