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

boost::thread or openMP for low-latency multi-threading
by Jack Bryan 19 Aug '11

19 Aug '11

Hi, I am trying to do parallelization for a computing intensive problem. I am working on a Linux cluster where each node is a multicore processor. e.g. 2 or 4 quad-core processor per node. I want to reduce latency and improve performance as much as possible. I plan to use multiprocessing and multithreading at the same. Each process run on a distinct node and each process spawn many threads on each node. This is a 2 level parallelism. For multiprocessing, I would like to choose MPI. For multithreading, I have two choices: openMP or boost::thread (pthread). Which one has lower latency and higher performance ? It seems that openMP coding is easier (without touching low level thread managing manually). But, it seems that openMP has higher overhead than boost::thread (pthread). Any help is really appreciated. thanks

1 0

Scoped Pairs of functions?
by Brian Allison 19 Aug '11

19 Aug '11

Hi all, I'm on a project which uses a C++ compiler, but with a lot of C-isms. One of those is that there are objects with pairs of functions which allocate/deallocate resources. I don't have time to fix all of the design issues with the classes that do this (yet), but within one compilation unit I'd like to remove the chance for leaks. So - if I wanted to use boost types to wrap around 2 functions f() and g(), where each function - has a void or primitive return type - takes zero or 1 argument - where f() is called at some point in a scope, and then g() is called *on exiting the scope *from which f() is called and only if f() doesn't throw.. - has its return value ignored. [Gahh....] Is there a boost::bind (or lambda) expression that I can wrap in a type? I'm not adverse to using several template parameters. If it were just nullary functions I could just use: struct Reference {}; struct TypeWrapper{}; // Signify something like shared_ptr, a T which wraps around a pointer to an object of the type containing the functions, where T has a typedef value_type to refer to the wrapped type, and a get() to obtain a pointer to the wrapped pointer. template<class T, type R1, type R2, class P = Reference> struct ScopedDuals { typedef R1 (T::*f_t)(); typedef R2 (T::*g_t)(); ScopedDuals(T&t, f_t f, g_t g) : t_(t), g_(g) { (t_.f)(); } ~ScopedDuals() { (t_.*g_)(); } private: T& t_; g_t g_; }; template<class T, type R1. type R2> struct ScopedDuals<T, R1, R2, TypeWrapper> { typedef typname T::value_type Inner_t; typedef R1 (Inner_t::*f_t)(); typedef R2 (Inner_t::*g_t)(); ScopedDuals(T&t, f_t f, g_t g) : t_(t), g_(g) { (t_.get()->*f)(); } ~ScopedDuals() { (t_.get()->*g_)(); } private: T& t_; g_t g_; }; How do I generalize to include the possibility of a single argument? and.... does anyone have a better suggestion for a name than "ScopedDuals"? While *I *think it's precise, it may not be useful to my teammates. thanks, Brian

2 3

dynamically linked libraries looking for static libraries which don't exist
by Pally Sandher 19 Aug '11

19 Aug '11

I've built debug binaries of boost 1.47.0 on Windows with MSVC 10 using the following options b2.exe variant=debug link=shared threading=multi runtime-link=shared which as far as I understand should build dynamically linked libraries (which it does, I get a bunch of .lib files & .dll files as expected). However when I try to link some projects in Visual Studio 2010 which import boost_filesystem-vc100-mt-gd-1_47.lib & boost_system-vc100-mt-gd-1_47.lib I get the following errors 1>LINK : fatal error LNK1104: cannot open file 'libboost_filesystem-vc100-mt-gd-1_47.lib' & 1>LINK : fatal error LNK1104: cannot open file 'libboost_system-vc100-mt-gd-1_47.lib' I can stop these errors by using the /NODEFAULTLIB option on both those libraries but I would like to stop them in the first instance. Does anyone have any ideas why the libraries which should be dynamically linked are looking for statically linked libraries which don't exist? Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer

3 3

Starting...
by Giordano Bruno 18 Aug '11

18 Aug '11

Hi people, I want to use boost_pp in my embedded systems development using avr-gcc (C language). I was trying to understand how boostpp works, but it looks fuzzy to me. Can you explain me what is this "0" in the line 40 from preprocessor/comparison/less.hpp: define BOOST_PP_LESS_D(d, x, y) BOOST_PP_IIF(BOOST_PP_NOT_EQUAL(x, y), BOOST_PP_LESS_EQUAL_D, 0 BOOST_PP_TUPLE_EAT_3)(d, x, y) http://www.boost.org/doc/libs/1_43_0/boost/preprocessor/comparison/less.hpp thanks Giordano >

2 1

Re: [Boost-users] : dynamically linked libraries looking for static
by Alex Perry 18 Aug '11

18 Aug '11

Pally Sandher <pally.sandher(a)iesve.com> wrote on Thu, 18 Aug 2011 15:49:07 +0000 > > I've built debug binaries of boost 1.47.0 on Windows with MSVC 10 using the > following options > snip > I can stop these errors by using the /NODEFAULTLIB option on both those > libraries but I would like to stop them in the first instance. Does anyone have > any ideas why the libraries which should be dynamically linked are looking for > statically linked libraries which don't exist? Are you using the appropriate #define in your consuming code Eg #ifndef BOOST_REGEX_DYN_LINK #define BOOST_REGEX_DYN_LINK #endif #include <boost/regex.hpp> Which would ask to link to the dynamic link version of regex library not the static one - then all you need to do is make sure that the path to the boost libraries directory is added rather than having to add specific libraries Similar defines exist for the other libraries which are not header only. HTH Alex

1 0

Why is asio clobbering my file before it can be sent?
by Andrew Yancy 18 Aug '11

18 Aug '11

I've used the same boilerplate boost::asio code for years to send a plain text file "foo.txt" from a server back to a client and it has always worked fine. Suddenly for no apparent reason, the same code I've always used with no problems now deletes the contents of foo.txt before it can actually be sent to the client. I'm creating foo.txt with a different program now, but I don't see how that could make any difference on Win32. Below is the relevant part of the code just before I use boost::asio::write to send the contents of foo.txt back to the client. As shown by the two printf statements, the contents of the file are somehow lost when the file name and size are sent to the client. Anyone know what's going on? Is there any other information I can provide to shed light on the problem? Thanks very much for any help~ std::ifstream source_file("foo.txt", std::ios_base::binary | std::ios_base::ate); if (!source_file) return __LINE__; size_t file_size = source_file.tellg(); source_file.seekg(0); printf("foo.txt size: %d\n", (int) file_size); //size is OK here boost::asio::streambuf request; std::ostream request_stream(&request); request_stream << return_fn << "\n" << file_size << "\n\n"; boost::asio::write(socket, request); file_size = source_file.tellg(); printf("foo.txt size: %d\n", (int) file_size); //size is now 0!

3 4

[IOStreams] Is such a behaviour considered as bug
by Ovanes Markarian 17 Aug '11

17 Aug '11

Hello *, I really enjoyed working with Iostreams, while testing some of my components. Using IOStreams with array_device seemed to be a very powerfull approach to test some of my stream based algorithms. But currently I face some issues which seem to be really weired to me. I produced some code snippet to better explain it. I used Boost.Test library to verify my assumptions. using namespace boost; namespace io=boost::iostreams; typedef unsinged char byte; typedef array<byte, 2> arr_buffer; //boost::array typedef io::basic_array<byte> arr_dev; arr_buffer buffer_ = {{}}; arr_dev dev_(buffer_.begin(), buffer_.end()); io::stream<arr_dev> ios_(dev_); arr_dev::pair_type range = dev_.input_sequence(); BOOST_MESSAGE("size: " << distance(range.first, range.second)); // output: size is 2 BOOST_CHECK_EQUAL(0u, ios_.tellg()); //stream is at position 0 as expected ios_.seekg(1); BOOST_CHECK_EQUAL(1u, ios_.tellg()); // stream is at position 1 as expected ios_.seekg(2); BOOST_MESSAGE("current pos: " << ios_.tellg()); // !!! stream is at position 2 ios_.seekg(3); BOOST_MESSAGE("current pos: " << ios_.tellg()); // stream is at position -1 BOOST_MESSAGE("eof: " << ios_.eof()); // !!! but eof is false If the defined stream is only 2 bytes long why is 2 a valid stream position? Why is eof always false? Do you think this behavior is buggy? I changed the same behavior to read bytes from stream and created an array of length 3, but passed the range of 2 bytes to the device ctor. This works as expected: arr_buffer buffer_ = {{'a', 'b', 'c'}}; arr_dev dev_(buffer_.begin(), buffer_.begin()+2); //range of 2 bytes is passed io::stream<arr_dev> ios_(dev_); arr_dev::pair_type range = dev_.input_sequence(); BOOST_MESSAGE("size: " << distance(range.first, range.second)); byte bt; BOOST_MESSAGE("current pos: " << ios_.tellg()); // prints 0 BOOST_CHECK_EQUAL(0u, ios_.tellg()); ios_.read(&bt, 1); BOOST_MESSAGE("retrieved: " << bt); // prints 'a' BOOST_MESSAGE("current pos: " << ios_.tellg()); //prints 1 BOOST_CHECK_EQUAL(1u, ios_.tellg()); ios_.read(&bt, 1); BOOST_MESSAGE("retrieved: " << bt); // prints 'b' BOOST_MESSAGE("current pos: " << ios_.tellg()); // !!! prints 2, why not -1??? ios_.read(&bt, 1); BOOST_MESSAGE("retrieved: " << bt); // still prints 'b' => nothing retrieved BOOST_MESSAGE("current pos: " << ios_.tellg()); // !!! now it prints -1 BOOST_MESSAGE("eof: " << ios_.eof()); // !!! now eof is true Any ideas why it behaves as described? With Kind Regards, Ovanes

2 2

[Date Time] format_date_parser.parse_date fails to compile with "treat wchar_t as builtin type" set to No
by Daniel Mitchell 17 Aug '11

17 Aug '11

Boost 1.47, using Visual Studio 2010 and Visual Studio 2008, with boost 1.47 both built myself from source and with boost from the boostpro installers. (and with boost 1.47 rebuilt myself with /Zwchar_t- in msvc.jam). If I set "treat wchar_t as builtin type" to "No", then the following code fails to compile: #include <boost/date_time/gregorian/gregorian.hpp> #include <boost/date_time/posix_time/posix_time.hpp> void parseDate() { std::locale locale; boost::date_time::format_date_parser<boost::gregorian::date, wchar_t> parser(L"", locale); boost::date_time::special_values_parser<boost::gregorian::date, wchar_t> svp; boost::gregorian::date date = parser.parse_date(L"", L"", svp); } It gives the following error: c:\users\danielm\downloads\boost_1_47_0\boost_1_47_0\boost\lexical_cast.hpp(1116): error C2535: 'bool boost::detail::lexical_stream_limited_src<CharT,Base,Traits>::operator >>(unsigned short &)' : member function already defined or declared with [ CharT=char_type, Base=base, Traits=traits ] c:\users\danielm\downloads\boost_1_47_0\boost_1_47_0\boost\lexical_cast.hpp(993) : see declaration of 'boost::detail::lexical_stream_limited_src<CharT,Base,Traits>::operator >>' with [ CharT=char_type, Base=base, Traits=traits ] c:\users\danielm\downloads\boost_1_47_0\boost_1_47_0\boost\lexical_cast.hpp(1524) : see reference to class template instantiation 'boost::detail::lexical_stream_limited_src<CharT,Base,Traits>' being compiled with [ CharT=char_type, Base=base, Traits=traits ] c:\users\danielm\downloads\boost_1_47_0\boost_1_47_0\boost\lexical_cast.hpp(1653) : see reference to function template instantiation 'Target boost::detail::lexical_cast<Target,src,false,char_type>(const std::basic_string<_Elem,_Traits,_Ax> &,CharT *,size_t)' being compiled with [ Target=short, _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t>, CharT=char_type ] c:\users\danielm\downloads\boost_1_47_0\boost_1_47_0\boost\lexical_cast.hpp(1641) : while compiling class template member function 'short boost::detail::lexical_cast_do_cast<Target,Source>::lexical_cast_impl(const Source &)' with [ Target=short, Source=src ] c:\users\danielm\downloads\boost_1_47_0\boost_1_47_0\boost\lexical_cast.hpp(1813) : see reference to class template instantiation 'boost::detail::lexical_cast_do_cast<Target,Source>' being compiled with [ Target=short, Source=src ] c:\users\danielm\downloads\boost_1_47_0\boost_1_47_0\boost\date_time\format_date_parser.hpp(72) : see reference to function template instantiation 'Target boost::lexical_cast<int_type,std::basic_string<_Elem,_Traits,_Ax>>(const Source &)' being compiled with [ Target=short, int_type=short, _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t>, Source=std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t>> ] c:\users\danielm\downloads\boost_1_47_0\boost_1_47_0\boost\date_time\format_date_parser.hpp(365) : see reference to function template instantiation 'int_type boost::date_time::fixed_string_to_int<short,charT>(std::istreambuf_iterator<_Elem,_Traits> &,std::istreambuf_iterator<_Elem,_Traits> &,boost::date_time::parse_match_result<charT> &,unsigned int,const charT &)' being compiled with [ int_type=short, charT=wchar_t, _Elem=wchar_t, _Traits=std::char_traits<wchar_t> ] c:\users\danielm\downloads\boost_1_47_0\boost_1_47_0\boost\date_time\format_date_parser.hpp(254) : while compiling class template member function 'boost::gregorian::date boost::date_time::format_date_parser<date_type,charT>::parse_date(std::istreambuf_iterator<_Elem,_Traits> &,std::istreambuf_iterator<_Elem,_Traits> &,std::basic_string<_Elem,_Traits,_Ax>,const boost::date_time::special_values_parser<date_type,charT> &) const' with [ date_type=boost::gregorian::date, charT=wchar_t, _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t> ] c:\source\dan\boost_wchar_t_test\boost_wchar_t_test\boost_wchar_t_test.cpp(18) : see reference to class template instantiation 'boost::date_time::format_date_parser<date_type,charT>' being compiled with [ date_type=boost::gregorian::date, charT=wchar_t ] If I set "wchar_t is builtin type" to Yes, then it compiles fine. Testing with #pragma message to verify things, BOOST_NO_INTRINSIC_WCHAR_T is defined (or not defined) appropriately depending on how I set that compiler option, so it looks as if Boost knows what's going on at that level. I've tried all the possible reconfigurations I can think of, but this error happens with the boostpro installs, with Boost built unchanged from the 1.47 distribution, and with Boost rebuilt with /Zwchar_t- set in msvc.jam. Is there a way to solve this? The issue originally appears when trying to build code from another library -- but this is a minimal repro it with just boost code, so I think it's a Boost problem, unless I'm missing something. thanks, -- dan

1 0

Boost.Bimap vector_of element access VS 9 compilation errors
by John Eddy 17 Aug '11

17 Aug '11

Hello, I’m having difficulty figuring out how to access elements from a vector_of view in a bimap. The following code does not compile in VS 2008. #include <string> #include <iostream> #include <boost/bimap/bimap.hpp> #include <boost/bimap/vector_of.hpp> using namespace std; using namespace boost::bimaps; int main() { typedef bimap< string, vector_of<int> > bimap_type; bimap_type bm; bm.insert(bimap_type::value_type("zero", 0)); bm.insert(bimap_type::value_type("one", 1)); const bimap_type::right_map& right = bm.right; // Both of the lines below cause compilation failure with vc++ 9.0. bm.right[0]; //bm.right.at(0); return 0; } Can anyone see what I’m doing wrong or is there some other means of accessing the elements of the map via the vector? Thanks, John

1 0

[thread] 1.47 on cygwin 1.7 -> undefined reference to boost::detail::set_tss_data::shared_ptr::tss_cleanup
by Frédéric Bron 17 Aug '11

17 Aug '11

I am trying to use boost 1.47 on cygwin 1.7 cross-compiling to win32 with i686-w64-mingw32-g++ (4.5.3). This program gives me an error: #include <boost/thread/tss.hpp> int main() { boost::thread_specific_ptr<int> ts; return 0; } $ i686-w64-mingw32-g++ -o mgw-release/obj/Tests/toto.o -c -O3 -DNDEBUG -Wall -Wextra -pipe -mthreads -I/cygdrive/d/Softs/1.7/mgw-release/boost/include -I. Tests/toto.cc In file included from /cygdrive/d/Softs/1.7/mgw-release/boost/include/boost/thread/detail/thread_heap_alloc.hpp:15:0, from /cygdrive/d/Softs/1.7/mgw-release/boost/include/boost/thread/tss.hpp:10, from Tests/toto.cc:1: /cygdrive/d/Softs/1.7/mgw-release/boost/include/boost/thread/win32/thread_heap_alloc.hpp:59:40: warning: inline function ‘void* boost::detail::allocate_raw_heap_memory(unsigned int)’ declared as dllimport: attribute ignored /cygdrive/d/Softs/1.7/mgw-release/boost/include/boost/thread/win32/thread_heap_alloc.hpp:69:39: warning: inline function ‘void boost::detail::free_raw_heap_memory(void*)’ declared as dllimport: attribute ignored $ i686-w64-mingw32-g++ -o mgw-release/bin/toto -O3 -DNDEBUG -Wall -Wextra -pipe -mthreads -I/cygdrive/d/Softs/1.7/mgw-release/boost/include mgw-release/obj/Tests/toto.o -Wl,--enable-auto-import -static -L/cygdrive/d/Softs/1.7/mgw-release/boost/lib -lboost_thread_win32 mgw-release/obj/Tests/toto.o:toto.cc:(.text+0x104): undefined reference to `__imp___ZN5boost6detail12set_tss_dataEPKvNS_10shared_ptrINS0_20tss_cleanup_functionEEEPvb' collect2: ld returned 1 exit status any help would be welcome. Regards, Frédéric

3 5

[Regex | Xpressive] Efficiently "grepping" large files
by Thomas Luzat 17 Aug '11

17 Aug '11

Hello, I am looking into Boost.Regex and Boost.Xpressive for implementing grep-like functionality on large files. More specifically I want to check whether a file contains a match for an expression which does not need that much context (a few KB). regex_search and BidirectionalIterators for the whole file work, but there is a complication: I want to do other operations on the file in other threads in parallel (such as calculating hashes and extracting other data). Given that this is mostly I/O bound I would like to avoid rereading portions of the file as much as possible. My idea was to implement a circular buffer which may block the workers (and reading, if data is ever read faster than analyzed). The circular buffer needs to know when old data is no longer required, though, that is regex_search no longer works on it or backtracks into it. The best idea so far is to read blocks of data and do slightly overlapped calls of regex_search on those blocks. This approach has got at least two problems: 1) Matches and context are potentially limited to the size of the overlap. 2) Semantics of the match might be changed if I choose an arbitrary cut for the overlap (e.g. ^ and $ might change because I cut the beginning or end of a line) I would not mind to specify a maximum context of a few KB to maybe 1 MB, but I do not want to change semantics. Is there a better approach? I was thinking about supplying some intelligent iterators, but Regex/Xpressive might leave copies around longer than I anticipate, such that I still cannot decide where they are and how far they may still backtrack. If that's not really possible with the boost libraries I would be interested in alternatives, too. I am already considering looking into some grep implementations. Thanks in advance! Thomas Luzat

3 5

cross-compiling didn't work with boost:filesystem
by rudy b 17 Aug '11

17 Aug '11

Hi, I developed a code on Linux, and the only library that I used was boost:filesystem. I was very happy with the code on Linux, and it never gave me a problem and never broke on me, I tried it on different scenarios and different file types, and I had never issue with boost::filesystem::remove(&path) function. But, now, I needed my code on a Mac machine (but I don't have a Mac) so I borrowed my friend's Mac, and installed xcode, and installed boost_1.47, and I didn't get a single error or warning when installing these packages. As a test, I even ran some simple filesystem examples that were provided. and they all passed. I even used the same "make" file that I had on linux, and it worked great on Mac. (no warnings when compiled) But, when I tried to run my code, I was getting errors with ::remove functions. I am not sure, but I think part of it was because I may have read-only permission on some of the files, and maybe that is why it complained, although I never had this problem in Linux. Also, another part of it could be because of the file naming with white space between its characters: (e.g. "my document.txt" because of this space). I don't know, but I thought that "boost::filesystem" should be independent of the developing platform, and that I could be fairly confident that if it works on one platform (Linux), it should be working on another one (Mac). Any idea, what I am doing wrong, and how this can be fixed? thanks, RB

2 1

[Containers Library Review] The review of the Containers library by Ion Gaztanaga starts today
by John Maddock 17 Aug '11

17 Aug '11

The review of the containers library by Ion Gaztanaga starts today, to summarize the library: "Boost.Container library implements several well-known containers, including STL containers. The aim of the library is to offers advanced features not present in standard containers or to offer the latest standard draft features for compilers that comply with C++03. In short, what does Boost.Container offer? * Move semantics are implemented, including move emulation for pre-C++0x compilers. * New advanced features (e.g. placement insertion, recursive containers) are present. * Containers support stateful allocators and are compatible with Boost.Interprocess (they can be safely placed in shared memory). * The library offers new useful containers: o flat_map, flat_set, flat_multiset and flat_multiset: drop-in replacements for standard associative containers but more memory friendly and with faster searches. o stable_vector: a std::list and std::vector hybrid with random-access iterators that offers iterator stability in insertions and erasures. o slist: the classic pre-standard singly linked list container." Documentation from the library may be viewed online here: file:///M:/data/boost/sandbox/move/libs/container/doc/html/index.html The source may be accessed from the "move" directory of the sandbox SVN or downloaded from http://www.drivehq.com/web/igaztanaga/boost_container.zip. Note that this download contains a copy of the accepted, but not yet release, Boost.Move library - extract the zip over a copy of Boost-1.47 to get a full working copy. Review comments might like to 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. Regards, John Maddock.

5 5

ublas bug?
by Peter Man 17 Aug '11

17 Aug '11

Hi, I was just wondering if there is a bug in ublas (boost version 1.47): when I use the following code (in debug mode): ublas::matrix<double> m; ublas::matrix<double> m2; m2 = m; this compiles in MSVC 10, but produces a runtime error "Expression: invalid null pointer". I had a look at some of the underlying ublas code, and found that default initialisation of matrices makes the underlying data pointer "data_" be set to NULL, and that when one matrix is copied to another, std::copy is invoked to copy one data_ to the other. However, I looked at the MSVC std::copy definition, and it seems to check for NULLness of the pointers. The following link explains this in more detail: https://connect.microsoft.com/VisualStudio/feedback/details/558044/std-copy… On the plus side, I have no such problem when running the above code in linux. Thanks, Peter

1 0

Simple inclusion of (1.47.0) filesystem.hpp generates compiler errors.
by Bill Moo 17 Aug '11

17 Aug '11

Hello Users, Qt v4.7.2 Boost v1.47.0. Intel Compiler v 12.0.1029.2010 Windows 7 Ultimate N x64 Building an x64 Release binary I have just included the boost/filesystem.hpp file in to my application and re-compiled only for the compiler to generate these errors. As yet I am not using any of the functionality of this I just included the file. Is this another Intel / MSVC STL issue? Sorry for the dump but without it I assume you won't be able to help. ..\Includes\boost/filesystem/v3/operations.hpp(126): error: expected either a definition or a tag name BOOST_SCOPED_ENUM_START(copy_option) ^ ..\Includes\boost/filesystem/v3/operations.hpp(127): error: expected an identifier {none, fail_if_exists = none, overwrite_if_exists}; ^ ..\Includes\boost/filesystem/v3/operations.hpp(127): error: expected a ";" {none, fail_if_exists = none, overwrite_if_exists}; ^ ..\Includes\boost/filesystem/v3/operations.hpp(150): error: identifier "copy_option" is undefined BOOST_SCOPED_ENUM(copy_option) option, // See ticket #2925 ^ ..\Includes\boost/filesystem/v3/operations.hpp(299): error: identifier "copy_option" is undefined BOOST_SCOPED_ENUM(copy_option) option) ^ ..\Includes\boost/filesystem/v3/operations.hpp(303): error: name followed by "::" must be a class or namespace name {detail::copy_file(from, to, copy_option::fail_if_exists);} ^ ..\Includes\boost/filesystem/v3/operations.hpp(306): error: identifier "copy_option" is undefined BOOST_SCOPED_ENUM(copy_option) option, system::error_code& ec) ^ ..\Includes\boost/filesystem/v3/operations.hpp(310): error: name followed by "::" must be a class or namespace name {detail::copy_file(from, to, copy_option::fail_if_exists, &ec);} ^ ..\Includes\boost/filesystem/v3/operations.hpp(642): error: expected either a definition or a tag name BOOST_SCOPED_ENUM_START(symlink_option) ^ ..\Includes\boost/filesystem/v3/operations.hpp(643): error: expected an identifier { ^ ..\Includes\boost/filesystem/v3/operations.hpp(643): error: expected a ";" { ^ ..\Includes\boost/filesystem/v3/operations.hpp(648): warning #12: parsing restarts here after previous syntax error }; ^ ..\Includes\boost/filesystem/v3/operations.hpp(651): error: identifier "symlink_option" is undefined BOOST_BITMASK(BOOST_SCOPED_ENUM(symlink_option)) ^ ..\Includes\boost/filesystem/v3/operations.hpp(651): error: identifier "symlink_option" is undefined BOOST_BITMASK(BOOST_SCOPED_ENUM(symlink_option)) ^ ..\Includes\boost/filesystem/v3/operations.hpp(651): error: identifier "symlink_option" is undefined BOOST_BITMASK(BOOST_SCOPED_ENUM(symlink_option)) ^ ..\Includes\boost/filesystem/v3/operations.hpp(651): error: nonmember operator requires a parameter with class or enum type BOOST_BITMASK(BOOST_SCOPED_ENUM(symlink_option)) ^ ..\Includes\boost/filesystem/v3/operations.hpp(651): error: identifier "symlink_option" is undefined BOOST_BITMASK(BOOST_SCOPED_ENUM(symlink_option)) ^ The two errors above are repeated and repeated many times so I removed then to save bandwidth, space and time. ..\Includes\boost/filesystem/v3/operations.hpp(662): error: name followed by "::" must be a class or namespace name recur_dir_itr_imp() : m_level(0), m_options(symlink_option::none) {} ^ ..\Includes\boost/filesystem/v3/operations.hpp(678): error: name followed by "::" must be a class or namespace name if ((m_options & symlink_option::_detail_no_push) == symlink_option::_detail_no_push) ^ ..\Includes\boost/filesystem/v3/operations.hpp(678): error: name followed by "::" must be a class or namespace name if ((m_options & symlink_option::_detail_no_push) == symlink_option::_detail_no_push) ^ ..\Includes\boost/filesystem/v3/operations.hpp(679): error: name followed by "::" must be a class or namespace name m_options &= ~symlink_option::_detail_no_push; ^ ..\Includes\boost/filesystem/v3/operations.hpp(682): error: name followed by "::" must be a class or namespace name || (m_options & symlink_option::recurse) == symlink_option::recurse)) ^ ..\Includes\boost/filesystem/v3/operations.hpp(682): error: name followed by "::" must be a class or namespace name || (m_options & symlink_option::recurse) == symlink_option::recurse)) ^ ..\Includes\boost/filesystem/v3/operations.hpp(737): error: identifier "symlink_option" is undefined BOOST_SCOPED_ENUM(symlink_option) opt = symlink_option::none) ^ ..\Includes\boost/filesystem/v3/operations.hpp(737): error: name followed by "::" must be a class or namespace name BOOST_SCOPED_ENUM(symlink_option) opt = symlink_option::none) ^ ..\Includes\boost/filesystem/v3/operations.hpp(747): error: identifier "symlink_option" is undefined BOOST_SCOPED_ENUM(symlink_option) opt, ^ ..\Includes\boost/filesystem/v3/operations.hpp(737): error: name followed by "::" must be a class or namespace name BOOST_SCOPED_ENUM(symlink_option) opt = symlink_option::none) ^ ..\Includes\boost/filesystem/v3/operations.hpp(761): error: name followed by "::" must be a class or namespace name m_imp->m_options = symlink_option::none; ^ ..\Includes\boost/filesystem/v3/operations.hpp(783): error: name followed by "::" must be a class or namespace name return (m_imp->m_options & symlink_option::_detail_no_push) ^ ..\Includes\boost/filesystem/v3/operations.hpp(784): error: name followed by "::" must be a class or namespace name == symlink_option::_detail_no_push; ^ ..\Includes\boost/filesystem/v3/operations.hpp(802): error: name followed by "::" must be a class or namespace name m_imp->m_options |= symlink_option::_detail_no_push; ^ ..\Includes\boost/filesystem/v3/operations.hpp(804): error: name followed by "::" must be a class or namespace name m_imp->m_options &= ~symlink_option::_detail_no_push; ^ ..\Includes\boost/filesystem/v3/operations.hpp(988): error: namespace "boost::filesystem3" has no member "copy_option" using filesystem3::copy_option; ^ ..\Includes\boost/filesystem/v3/operations.hpp(1031): error: namespace "boost::filesystem3" has no member "symlink_option" using filesystem3::symlink_option; ^ -- Bill

1 0