August 2011 - Boost-users - lists.preview.boost.org

Serialization: how to port binary archives containing NAN created with version 1.43 to version 1.47?
by Robert Lupton the Good 21 Aug '11

21 Aug '11

>> Because of a user request we support serialization of nan and inf. >> The official boost archives don't, as you already found out. > Robert Ramey wrote: > I just looked at the page. It looks very interesting to me. When > I have some time, I will be investigating which of these might > be included in the boost distribution of the serialization library. Does this mean that you plan to support IEEE special values (e.g. NaN, Inf) in boost, or some other part of Christian's work? There's traffic on the IEEE limitation (feature?) in boost::serialize dating back to at least 2005 --- some with your name on it! R

2 1

[iostreams] encryption filters
by Sean Farrow 21 Aug '11

21 Aug '11

Hi: Has anybody written encryption filters for the IOStreams library using crypto++? I need to do this but didn't want to duplicate effort if any existed already. Cheers Sean.

1 0

[Serialization] Prevent member serialization in a non intrusive situation
by Sean Farrow 21 Aug '11

21 Aug '11

Hi: I am using boost.serialization, and need to prevent members (boost.thread, and Booleans) being serialized. Given that I am using non-intrusive serializing code, what is the best way of doing this. Any help appreciated. Cheers Sean.

1 0

boost 1.47.0 failed to be built under MinGW...
by JIA Pei 21 Aug '11

21 Aug '11

Hi, all: Happened to notice that boost 1.47.0 is out, therefore, I just downloaded boost_1_47_0.zip and would like to try it out . However, I wanna try to use MinGW to build boost this time. 1) I strictly followed http://www.boost.org/doc/libs/1_47_0/more/getting_started/windows.html 2) Also, I referred to http://cboard.cprogramming.com/windows-programming/126599-how-set-boost-up-… However I always obtain the following errors: > Failed to bootstrap the build engine Consult 'bootstrap.log' for more details In bootstrap.log, I had the following error messages: > builtins.c:32:23: fatal error: sys/wait.h: No such file or directory > compilation terminated. > execunix.c:17:26: fatal error: sys/resource.h: No such file or directory > compilation terminated. > fileunix.c:98:17: fatal error: ar.h: No such file or directory > compilation terminated. The reason seems to be in the current installed MinGW (the newest version), there seems to be no sys/wait.h sys/resource.h ar.h What's more, from http://patchwork.ozlabs.org/patch/74260/ it's suggested that "Don't use sys/wait.h for mingw targets" . It could be this reason that sys/wait.h is not included in current MinGW installation, which actually influence the current boost 1.47.0's bootstrap !!! Can anybody give me a hand on this? Cheers Pei -- Pei JIA Email: jp4work(a)gmail.com cell: +1 604-362-5816 Welcome to Vision Open http://www.visionopen.com

1 0

Boost Graph Very Strange Behavior
by Alexander Feldman 21 Aug '11

21 Aug '11

Dear All, I have upgraded to Boost 1.47.0 and I have spent a day on the following strange behavior that someone who knows Boost better may explain to me. Consider the source below. If I uncomment the line: //cout << ""; in line 39, then the program starts working, i.e., it outputs: 0x1 If I comment out line 39, then I get 0 There are no memory leaks. This kind of stuff gives me nightmares. Thanks for your help and sorry for the longish example. Thanks, -- Alex ----------------------------------------------------------------------- #include <boost/graph/adjacency_list.hpp> #include <iostream> using namespace boost; using namespace std; typedef adjacency_list<listS, listS, undirectedS, property<vertex_name_t, void *>, property<edge_name_t, void *> > GraphT; class Graph : public GraphT { public: Graph(); public: typedef graph_traits<GraphT>::vertex_descriptor VertexType; typedef graph_traits<GraphT>::edge_descriptor EdgeType; public: ostream &put(ostream &) const; void setNetLabel(const EdgeType &, void *); void addNet(const VertexType &, const VertexType &, void *); private: property_map<GraphT, edge_name_t>::type net_; }; Graph::Graph() { net_ = get(edge_name, *this); } void Graph::setNetLabel(const EdgeType &edge, void *label) { //cout << ""; net_[edge] = label; } void Graph::addNet(const VertexType &branch1, const VertexType &branch2, void *label) { EdgeType ei; bool inserted; tie(ei, inserted) = add_edge(branch1, branch2, *this); if (inserted) { setNetLabel(ei, label); } } ostream &Graph::put(ostream &out) const { graph_traits<GraphT>::edge_iterator ei, ei_end; for (tie(ei, ei_end) = edges(*this); ei != ei_end; ei++) { out << net_[*ei] << endl; } return out; } int main(int argc, char **argv) { Graph graph; Graph::VertexType v1 = add_vertex(graph); Graph::VertexType v2 = add_vertex(graph); graph.addNet(v1, v2, (void *)1); graph.put(cout); return EXIT_SUCCESS; } -----------------------------------------------------------------------

2 2

[serialization] : compile problem
by Kaz 20 Aug '11

20 Aug '11

Hi All, I am trying to compile this code to test boost serialization, however I am getting this error Error 5 error C2664: 'boost::mpl::assertion_failed' : cannot convert parameter 1 from 'boost::mpl::failed ************boost::serialization::is_wrapper<T>::* ***********' to 'boost::mpl::assert<false>::type' c:\program files (x86)\boost\boost_1_46_1\boost\archive\basic_xml_oarchive.hpp 92 I am using boost 1.46.1, visual studio c++ 2010 express. Any help will be appreciated. Thanks, Kaz //----------------------------------------------------------------------------------------------------------- #include <string> #include <boost/serialization/vector.hpp> #include <boost/serialization/list.hpp> #include <boost/archive/xml_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/tmpdir.hpp> #include <fstream> class Base { friend class boost::serialization::access; template<typename archive> void serialize( archive& ar, const unsigned int version ) { ar & BOOST_SERIALIZATION_NVP(a) & BOOST_SERIALIZATION_NVP(c) & BOOST_SERIALIZATION_NVP (strBase); } public: Base( int a_arg, char c_arg ) : a( a_arg ), c ( c_arg ) { strBase = "This is base"; } int a; char c; std::string strBase; }; //------------------------------------- BOOST_SERIALIZATION_ASSUME_ABSTRACT(Base) //------------------------------------- class Child : public Base { friend class boost::serialization::access; template<typename archive> void serialize( archive& ar, const unsigned int version ) { ar & boost::serialization::base_object<Base>(*this); ar & BOOST_SERIALIZATION_NVP(f) & BOOST_SERIALIZATION_NVP(strChildName); } public: Child() : Base(0,'c'), f(3.3417) { strChildName = "This is Child"; } float f; std::string strChildName; }; //------------------------------------- class BaseContainer { typedef Base* BasePtr; std::vector<BasePtr> BaseVec; friend class boost::serialization::access; template<typename archive> void serialize( archive& ar, const unsigned int version ) { ar.register_type<Base>(); ar.register_type<Child>() ; ar & BaseVec; } public: BaseContainer() {} void Init() { for(int i = 0; i < 10; ++i ) { if ( i < 5 ) BaseVec.push_back( new Base(i,'b') ); else BaseVec.push_back( new Child() ); } } }; //------------------------------------- int main() { std::string filename="demo.xml"; BaseContainer baseContainer; baseContainer.Init(); { std::ofstream ofile(filename); boost::archive::xml_oarchive out(ofile); out << BOOST_SERIALIZATION_NVP(baseContainer); } return 0; } //-------------------------------------

2 2

Re: [Boost-users] Boost asio deadline_timer, bug?
by Marat Abrarov 20 Aug '11

20 Aug '11

Hi, Allan. > Is this a bug, or am I doing something wrong? Note that deadline_timer always (!) invokes wait handler, even it was successfully cancelled (int res = timer1.cancel(); assert(res > 0);): http://www.boost.org/doc/libs/1_47_0/doc/html/boost_asio/reference/basic_de… ~~~ The handler for each cancelled operation will be invoked with the boost::asio::error::operation_aborted error code. ~~~ Regards, Marat Abrarov.

2 1

[review] Conversion review starts today
by Gordon Woodhull 20 Aug '11

20 Aug '11

Hi All, The review of Vicente Botet Escriba's Conversion library starts today and ends August 29. The Conversion library manages generic explicit conversion between unrelated types. It can be thought of as a substitute for overloading static_cast, or as an alternative to lexical_cast when conversion via text is unwanted. The code is available here: http://svn.boost.org/svn/boost/sandbox/conversion/ And the documentation is here: http://svn.boost.org/svn/boost/sandbox/conversion/libs/conversion_ext/doc/h… Alternately, you can download a compressed package here: https://github.com/viboes/TBoost.Conversion Reviews may answer the following questions: * 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. Of course, "informal reviews" and discussion are also welcome. Cheers, Gordon Woodhull Espen Harlinn

1 0

[boost] [review] Conversion review starts today
by Gordon Woodhull 20 Aug '11

20 Aug '11

Hi All, The review of Vicente Botet Escriba's Conversion library starts today and ends August 29. The Conversion library manages generic explicit conversion between unrelated types. It can be thought of as a substitute for overloading static_cast, or as an alternative to lexical_cast when conversion via text is unwanted. The code is available here: http://svn.boost.org/svn/boost/sandbox/conversion/ And the documentation is here: http://svn.boost.org/svn/boost/sandbox/conversion/libs/conversion_ext/doc/h… Alternately, you can download a compressed package here: https://github.com/viboes/TBoost.Conversion Reviews may answer the following questions: * 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. Of course, "informal reviews" and discussion are also welcome. Cheers, Gordon Woodhull Espen Harlinn _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [Boost-users] [Containers Library Review] The review of the Containers library by Ion Gaztanaga starts today
by Ion Gaztañaga 20 Aug '11

20 Aug '11

El 17/08/2011 5:12, Edward Diener escribió: > I think the documentation is good, but it is hard to find overviews of > the separate containers. They are buried in the reference whereas I > would like to see them as separate topics in the TOC. It seems that documentation is the main issue of the review, I hope tools like autoindex will help me improve this and still maintain automatic reference documentation. > For the example in the "Emplace: Placement insertion" topic there is a > 'non_copy_movable ncm;' in the main function but it is never used, which > is confusing. I did get the idea of emplacement from the example and > understand what it is. Thanks for spotting this. > There is mention in the Introduction that "Containers support stateful > allocators" but that appears to be all that is written about that topic. > I would like to know what that is about. Ok, this has been already requested, I'll fix it. > The "Recursive Containers" topic gives a nice example but does not > explain what a recursive container entails and why a recursive container > is not guaranteed by the standard. Some further information should be > given in this topic. Ok > For all of the containers which have the same names as the std:: > containers, it should be pointed out what their benefits are. if it is a > matter of all those containers having move semantics, placement > insertion, recursive containers, and stateful allocators, that should be > mentioned. One would like to know why one should use the Containers > library containers rather than the std:: containers without having to > read the description of each container. Ok Best, Ion

3 6