- Boost-users - lists.boost.org

Using Variant with StateChart events
by Federico J. Fernández 22 Mar '07

22 Mar '07

Hi Boosters! I have been trying to use those libraries together. To be concrete, I want to have a variant of boost::statechart::event derived classes. The problem is that when I try to compile it I receive a lot of error messages, but the important ones say that there is no match for "operator new".. I mean, variant is calling a prototype of operator new that event doesn't offer. This is the error that I get: /usr/include/boost/variant/variant.hpp: In constructor 'boost::variant<T0, T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>::variant() [with T0_ [...] /usr/include/boost/variant/variant.hpp:1174: error: no matching function for call to 'evt_reset::operator new(unsigned int, void*)' /usr/include/boost/statechart/event.hpp:38: note: candidates are: static void* boost::statechart::event<MostDerived, Allocator>::operator new(size_t) [with MostDerived = evt_reset, Allocator = std::allocator<void>] Any idea? I want to have a container of this "events" and don't want to have a base class and working with virtual functions. Thanks!

2 1

Statechart current status
by Philippe DAVID 22 Mar '07

22 Mar '07

Hi, I'm interested in using the statechart library and I would like to know what its current status is. It looks like it is inactive since dec 2005, am I right ? Has the project been freezed ? Btw, why is statechart not included with the other boost libs ? Thanks, Philippe

2 1

[Serialization, XML] - how to avoid another encoding level
by Frank Bergemann 22 Mar '07

22 Mar '07

Hi, i am working with MICO and use boost::serialization (XML) for import/export of CORBA functions IN/OUT parameters, because i have an XML formatted configuration for the data to use for CORBA service invocations. One of the problems was, that some of the MICO are template'd. E.g. a data type holding a number of digits (e.g. telephone #no) is encoded in MICO as: template <class T, int TID, int max> class BoundedSequenceTmpl { ... } ... using basic <class T> = CORBA::Short for digits (e.g.). 1st i used ToString(...)/fromString(...) functions to be able to save&load such to/from boost archives. And this worked - though it had the little drawback, that i needed to use additional variables in load() & save() to handle it this way. But then next it came up, that some other CORBA data types use the BoundedSequenceTempl<> as well, but for _more complex_ <class T> - e.g. BoundedSequenceTempl<> of BoundedSequenceTempl<>. For that i created a version of serialize(), save() & load() like this: template<class Archive, class T, int TID, int max> void serialize(Archive & ar, BoundedSequenceTmpl<T, TID, max> &p, const unsigned int version) { split_free(ar, p, version); } template<class Archive,class T, int TID, int max> void save(Archive & ar, const BoundedSequenceTmpl<T, TID, max> &p, const unsigned int version) { unsigned long length = p.length(); ar & make_nvp("length", length); for (unsigned long i = 0; i < length; ++i) { std::ostringstream name; name << "item_" << i; ar & make_nvp(name.str(), p[i]); } } template<class Archive, class T, int TID, int max> void load(Archive & ar, BoundedSequenceTmpl<T, TID, max> &p, const unsigned int version) { unsigned long length; ar & make_nvp("length", length); p.length(length); for (unsigned long i = 0; i < length; ++i) { std::ostringstream name; name << "item_" << i; ar & make_nvp(name.str(), p[i]); } } then i thought i can get rid of the formerly used ToString(...)/FromString(...) helpers and replace them by overloaded versions of the new (more generic) load() & save() variants dedicated for this BoundedSequenceTempl<...>. Like this: #if 0 // This was intended to make obsolete MicoVector_to_string(...) & // MicoVector_from_string(...) // kind of "template specialization" for the ones above // for BoundedSequenceTmpl<...> of types, which we don't want // to be spread out any further // // But i couldn't make this work. // Means: it compiles. But it implies another XML encoding level // - which is not what i want template<class Archive, int TID, int max> void serialize(Archive & ar, BoundedSequenceTmpl<CORBA::Short, TID, max> &p, const unsigned int version) { split_free(ar, p, version); } template<class Archive, int TID, int max> void save (Archive & ar, const BoundedSequenceTmpl<CORBA::Short, TID, max> &p, const unsigned int version) { std::ostringstream ostream; for (unsigned long i=0; i<p.length(); ++i) { ostream << p[i]; } // tried this, but it didn't work (compilation failed): ar & str; // so i tested this option std::string str(ostream.str()); ar & make_nvp("hallo", str); // CREATES ANOTHER ENCODING LEVEL :-( } template<class Archive, int TID, int max> void load (Archive & ar, BoundedSequenceTmpl<CORBA::Short, TID, max> &p, const unsigned int version) { ... } #endif But that created me another level of encoding - which i don't want. E.g. having a superior encoder: template<class Archive> void save(Archive & ar, const DeleteHlrSubscriber_s &pInstance, const unsigned int version) { std::string simsi; std::string smsisdn; MicoVector_to_string(pInstance.imsi, simsi); MicoVector_to_string(pInstance.msisdn, smsisdn); // ar & make_nvp("imsi", simsi); // replace by the next... // this worked, but see above (the by "#if 0" disabled stuff) ar & make_nvp("imsi", pInstance.imsi); ar & make_nvp("msisdn", smsisdn); ar & make_nvp( "attach_imsi", pInstance.attach_imsi); } using pInstance.imsi directly (which is a BoundedSequenceTmpl<CORBA::Short>()) resulted in: <imsi> // dropped boost::serializations internal XML attributes here <hallo>SomeString</hallo> </imsi> But I would like to have this one <imsi>SomeString</imsi> How can i do that? Thanks! Best regards! Frank _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 3

[multi_index] function object as key extractor?
by Boris 22 Mar '07

22 Mar '07

As I find myself replacing all kind of C++ standard containers with multi_index_container (a really very useful container) I've been defining key extractors quite a lot and wonder if there is any shortcut like using lambda expressions or function objects. Here's some pseudo-code to explain what I mean: struct foo { std::string s; foo(std::string s) : s(s) { } }; typedef multi_index_container< foo, indexed_by< hashed_unique< boost::bind<std::size_t, &std::string::size, member<foo, std::string, &foo::s> > > > > mi_t; The idea is to call another function on the object which is returned by the key extractor member. Here in this example the multi_index_container would only store strings with a unique size. However I'm lost how to define the key extractor. The difficulty is probably that I normally don't need to specify types when I use boost::bind or lambda expressions. Now I need to figure out how to use them with multi_index_container - is there any trick or I better go on defining key extractors? Boris

6 21

Review of Intrusive library begins today March 12
by Joaquín Mª López Muñoz 22 Mar '07

22 Mar '07

The review of Ion Gaztañagas's Intrusive library begins today, March 12, and extends up to March 21. * Download: Boost vault: http://boost-consulting.com/vault/ Folder: Containers File: intrusive.2007-03-04.zip * Online docs: http://ice.prohosting.com/newfunk/boost/libs/intrusive * Description: Intrusive is a library presenting some intrusive containers to the world of C++. While intrusive containers were and are widely used in C, they became more and more forgotten in C++ due to the presence of the standard containers, which don't support intrusive techniques. Intrusive not only reintroduces this technique to C++, but also encapsulates the implementation in STL-like interfaces. Hence anyone familiar with standard containers can easily use Intrusive. Like their STL-counterparts, intrusive containers use template parameters to control the stored data types and some special aspects of intrusive containers. * Compilers tested (so far): Visual 7.1/WinXP Visual 8.0/WinXP GCC 4.1.1/MinGW Intel 9.1/WinXP GCC 4.1.2/Linux * Review questions: Here are some questions you might want to answer in your review: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? And finally, every review should answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. I invite you to submit your review, either publicly to the developers or the users lists, or else, if for whatever reason you don't want to publicize it, directly to me. Thank you for investing some of your time on reviewing Ion Gaztañaga's Intrusive library. The Review Manager, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

4 4

End of Intrusive library review period
by Joaquín Mª López Muñoz 22 Mar '07

22 Mar '07

The official period for the formal review of Ion Gaztañagas's Intrusive has finished on March 21, although there is no problem with continuing the ongoing discussions or submiting past last minute reviews during a few days. I plan to compile the contributions and publish the final result by the end of the next week. Thank you to all the participants for the quality and quantity of their contributions. The Review Manager, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[BGL] dfs on graphs with bundled-properties
by Naomi Fox 22 Mar '07

22 Mar '07

I am trying to use an adjacency list with bundled properties and running into lots of problems. I'm wondering if bundled properties is mature enough, or if I should resort to the older style using property maps. Here's a description of one problem I've run into: So I define my graph class with bundled properties as so: struct MyV { int numStars; }; struct MyE { int numStars; }; typedef adjacency_list<setS, setS, bidirectionalS, MyV, MyE> MyGraph; I would like to perform dfs on this graph. So I have a very simple visitor defined: struct star_visitor : public boost::default_dfs_visitor { template <class Vertex, class Graph> void start_vertex(Vertex v, const Graph &) { std::cout << 'start'; } template <class Vertex, class Graph> void discover_vertex(Vertex v, const Graph &) { std::cout << "*"; } template <class Vertex, class Graph> void finish_vertex(Vertex v, const Graph &) { std::cout << 'finish'; } }; Then in my main function, I make a MyGraph object and put in vertices and edges, and assign property values. That works fine. MyGraph g; MyGraph::vertex_descriptor v1 = addVertex(g); MyGraph::vertex_descriptor v2 = addVertex(g); MyGraph::edge_descriptor e2 = addEdge(v1, v2, g); g[*v1].numStars = 100; g[*v2].numStars = 2; g[*e1].numStars = 7; Then I perform dfs on my graph depth_first_search(g, visitor(star_vis)); And I get the following errors. I don't get these errors and my program compiles fine if I do a dfs with my star_visitor on a graph with no properties. Main.cpp c:\boost_1_33_1\boost\property_map.hpp(349) : error C2679: binary '+' : no operator found which takes a right-hand operand of type 'const boost::detail::error_property_not_found' (or there is no acceptable conversion) c:\program files\microsoft visual studio 8\vc\include\vector(366): could be 'std::_Vector_iterator<_Ty,_Alloc> std::_Vector_iterator<_Ty,_Alloc>::operator +(__w64 int) const' with [ _Ty=boost::default_color_type, _Alloc=std::allocator ] while trying to match the argument list '(const std::_Vector_iterator<_Ty,_Alloc>, const boost::detail::error_property_not_found)' with [ _Ty=boost::default_color_type, _Alloc=std::allocator ] c:\boost_1_33_1\boost\property_map.hpp(349) : while compiling class template member function 'boost::default_color_type boost::iterator_property_map::operator [](void *) const' with [ RandomAccessIterator=std::_Vector_iterator>, IndexMap=boost::adj_list_vertex_property_map, T=boost::default_color_type, R=boost::default_color_type & ] c:\documents and settings\istreinu\desktop\naomi\boost_1_33_1\boost\graph\depth_first_search.hpp(250) : see reference to class template instantiation 'boost::iterator_property_map' being compiled with [ RandomAccessIterator=std::_Vector_iterator>, IndexMap=boost::adj_list_vertex_property_map, T=boost::default_color_type, R=boost::default_color_type & ] c:\documents and settings\istreinu\desktop\naomi\boost_1_33_1\boost\graph\depth_first_search.hpp(332) : see reference to function template instantiation 'void boost::detail::dfs_dispatch::apply(const VertexListGraph &,DFSVisitor,Vertex,const boost::bgl_named_params &,boost::detail::error_property_not_found)' being compiled with [ VertexListGraph=MyGraph, DFSVisitor=Star_visitor, Vertex=void *, T=Star_visitor, Tag=boost::graph_visitor_t, Base=boost::no_property ] c:\documents and settings\istreinu\my documents\visual studio 2005\projects\refactorfirst\refactorfirst\main.cpp(228) : see reference to function template instantiation 'void boost::depth_first_search(const VertexListGraph &,const boost::bgl_named_params &)' being compiled with [ VertexListGraph=MyGraph, T=Star_visitor, Tag=boost::graph_visitor_t, Base=boost::no_property ]

2 1

which one is preferable vector (or similar things) or valarray (or similar things ) ?
by abir basak 22 Mar '07

22 Mar '07

Hi, I am using vector and similar containers extensively for my project, as well as boost circular_buffer_space_optimized (and adobe circular_queue which is built over vector ). They all work with iterator based concept. As I need to refer a portion of the vector (or circular buffer ) from within a class , I need to store index (not iterators, as container elements are movable ) or a pair of index within the class (using std::distance to get index from iterator, all of my containers are random access ). now from index , I create boost sub_range and use it. For arbitrary access, I store a vector<size_t>, and use boost permutation_iterator with the index. One point here, iterator is not very cheap when it is circular_buffer (and space optimized version) , as it is not merely a pointer , and it need to know container (i.e. store a ref to container) or store 3 pointers, one current pos, one for begin of buffer, one end of buffer (AFAIK boost uses former version). But after that I came to a different concept , a concept of view, which is used by boost uBLAS containers Blitz array and the STL low profile container valarray. Now it seems slice_view , range_view are cheaper for circular buffer, as only one reference to container is stored (esp when using permutation_iterator or arbitrary sequence access). Also seems cross referencing from one valarray to another is easier due to slice concept which can be directly stored. and it also provides some numeric operations. In my case all of the arrays are one dimensional, and they are array of some small struct (like point, tangent etc) most of them have some geometric meaning. And mostly I want to have some numeric operations on them (my original test implementation is in matlab and the array in matlab is just like Blitz array with little more overhead) I am little confused at this stage, which one to use. and if I use valarray kind of thing , how to use stl algorithm's with it (i.e how to get a iterator from it ? valarray is continuous so getting iterator is not a problem, but not sure whether I can sort a slice) . Can anyone help in this regard? abir -- Abir Basak, Member IEEE Software Engineer, Read Ink Technologies B. Tech, IIT Kharagpur email: abir(a)abirbasak.com homepage: www.abirbasak.com

1 0

ptr_sequence and transfer functions.
by Matthew Bray 22 Mar '07

22 Mar '07

I have a problem with the current ptr_sequence interface, according to the documentation point #7 at this location: http://www.boost.org/libs/ptr_container/doc/examples.html#transferring-owne… it should be possible to write something such as this ptr_list<X> list; ptr_vector<X> vec; list.transfer( list.begin(), vec.begin(), vec ); vec.transfer( vec.end(), list.begin(), list.end(), list ); i.e. given a U<T> and a V<T> I should be able to perform transfer operations in either direction. However given a suitable X this code fails to compile on VC++ 8 as well as GCC 3.4. Indeed any attempt to transfer between different ptr_sequence types (e.g. ptr_deque<X> to ptr_vector<X>) fails to compile. Looking at the implementation of ptr_sequence it appears easy to see why this is the case. However my question is is the documentation incorrect or is the current code incorrect? Right now if I wish to create containers of objects and then transfer ownership to others I'm forced to use the same container type throughout (i.e. the transfer functions provide no benefit at all if I have to choose the wrong container for the job), either that or write awkward transferal code when it appears the simple transfer function should do the job. Could someone please explain the situation regarding the transfer functions and documentation at this time? Thanks, Mat.

2 4

[Date_Time] undefined reference to as_short_string()
by Artus 22 Mar '07

22 Mar '07

Hi, I am trying to use Boost.Date_Time (and Boost) for the first time, and I failed to compile the following : ------------------------------------ #include <iostream> #include <iomanip> #include <boost/date_time/gregorian/gregorian.hpp> #include <boost/date_time/posix_time/posix_time.hpp> int main(int, char **) { using namespace std; using namespace boost::posix_time; using namespace boost::gregorian; std::cout << to_simple_string(second_clock::universal_time()); return 0; } ----------------------------------------- I get these comments : g++ -c -pipe -Wall -W -O2 -g -pipe -m32 -march=i386 -mtune=pentium4 -DQT_NO_DEBUG -DQT_SHARED -DQT_THREAD_SUPPORT -I/usr/lib/qt-3.3/mkspecs/default -I. -I/usr/lib/qt-3.3/include -o receiver.o receiver.cpp g++ -o receiver.exe receiver.o -L/usr/lib/qt-3.3/lib -L/usr/X11R6/lib -lchoo -lqt-mt -lXext -lX11 -lm receiver.o(.text+0xb96): In function `main': /usr/include/boost/date_time/date_formatting.hpp:43: undefined reference to `boost::gregorian::greg_month::as_short_string() const' I found some threads about this error but no solution. Can any one help? I am using Boost 1.32.0. Cheers, Patrick

1 0