- Boost - lists.boost.org

[quickbook] Failure building on trunk
by Edward Diener 27 Aug '11

27 Aug '11

Trying to generate some documentation using the latest on Boost trunk, the build of quickbook works with gcc but failed using toolset-msvc-10.0 with: "compile-c-c++ C:\Programming\VersionControl\boost\bin.v2\tools\quickbook\src\msvc-10.0\release\link-static\threading-multi\id_generator.obj id_generator.cpp C:\Programming\VersionControl\boost\boost/unordered/detail/buckets.hpp(220) : error C2668: 'boost::addressof' : ambiguous call to overloaded function C:\Programming\VersionControl\boost\boost/utility/addressof.hpp(51): could be 'T *boost::addressof<boost::unordered::detail::bucket<A>>(T &)' with [ T=boost::unordered::detail::bucket<std::allocator<std::pair<const std::string,quickbook::id_generator::id>>>, A=std::allocator<std::pair<const std::string,quickbook::id_generator::id>> ] C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\xmemory(109): or '_Ty *std::addressof<boost::unordered::detail::bucket<A>>(_Ty &)' [found using argument-dependent lookup] with [ _Ty=boost::unordered::detail::bucket<std::allocator<std::pair<const std::string,quickbook::id_generator::id>>>, A=std::allocator<std::pair<const std::string,quickbook::id_generator::id>> ] while trying to match the argument list '(boost::unordered::detail::bucket<A>)' with [ A=std::allocator<std::pair<const std::string,quickbook::id_generator::id>> ] C:\Programming\VersionControl\boost\boost/unordered/detail/buckets.hpp(207) : while compiling class template member function 'void boost::unordered::detail::buckets<A,Unique>::delete_buckets(void)' with [ A=std::allocator<std::pair<const std::string,quickbook::id_generator::id>>, Unique=true ] C:\Programming\VersionControl\boost\boost/unordered/detail/table.hpp(564) : see reference to class template instantiation 'boost::unordered::detail::buckets<A,Unique>' being compiled with [ A=std::allocator<std::pair<const std::string,quickbook::id_generator::id>>, Unique=true ] C:\Programming\VersionControl\boost\boost/unordered/detail/unique.hpp(392) : see reference to class template instantiation 'boost::unordered::detail::types<K,V,H,P,A,E,Unique>' being compiled with [ K=std::string, V=std::pair<const std::string,quickbook::id_generator::id>, H=boost::hash<std::string>, P=std::equal_to<std::string>, A=std::allocator<std::pair<const std::string,quickbook::id_generator::id>>, E=boost::unordered::detail::map_extractor<std::string,std::pair<const std::string,quickbook::id_generator::id>>, Unique=true ] C:\Programming\VersionControl\boost\boost/unordered/unordered_map.hpp(63) : see reference to class template instantiation 'boost::unordered::detail::map<K,H,P,A>' being compiled with [ K=std::string, H=boost::hash<std::string>, P=std::equal_to<std::string>, A=std::allocator<std::pair<const std::string,quickbook::id_generator::id>> ] c:\programming\versioncontrol\boost\tools\quickbook\src\id_generator.hpp(52) : see reference to class template instantiation 'boost::unordered::unordered_map<K,T>' being compiled with [ K=std::string, T=quickbook::id_generator::id ] call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"C:\Programming\VersionControl\boost\bin.v2\tools\quickbook\src\msvc-10.0\release\link-static\threading-multi\id_generator.obj.rsp" ...failed compile-c-c++ C:\Programming\VersionControl\boost\bin.v2\tools\quickbook\src\msvc-10.0\release\link-static\threading-multi\id_generator.obj..."

3 5

Re: [boost] [proto] Problems with operator <<
by John Maddock 27 Aug '11

27 Aug '11

> Folks, > > I'm having no end of problems with operator<< and proto. > > In the beginning, operator << was overloaded for stream output and > everything worked OK, then I added the left shift operator<< to the list > of protoized operators in the grammar and everything broke. The strange > thing is that: > > std::cout << a+b; > > correctly finds my stream out overload: > > template <class Exp> > inline std::ostream& operator << (std::ostream& os, const > big_number_exp<Exp>& r) > > But > > std::cout << a; > > no longer calls: > > template <class Backend> > inline std::ostream& operator << (std::ostream& os, const > big_number<Backend>& r) > > But calls the proto << operator instead. > > I'm at a complete loss to explain this, both of my overloads are in the > same namespace as their respective types, and as far as I can see both > should be preferred to the proto versions. To answer my own question - in case anyone else gets bitten by this - the answer is you need to provide overloads with both const and non-const reference RHS arguments to effectively hide the proto operator versions. Still some hair left yours.... John.

2 11

[program_options] Some methods take const char*, others take std::string
by Gabriel Redner 27 Aug '11

27 Aug '11

Hi all, Some methods in program_options accept const char*s (e.g. option_description constructor), while others take const std::string&s (e.g. option_description::key). This makes no difference to the user if he is passing string literals, but becomes annoying if he wants to pass strings, or expressions which return strings. Of course he can put (...).c_str() everywhere, but this is ugly and unnecessary, since program_options just takes its parameters and shoves them into string variables anyways. Since changing the parameter types to const std::string& should not break existing code, I do not see a downside to doing so (plus, it would allow me to get rid of .c_str()s everywhere :-). Does it seem reasonable for program_options public APIs to accept std::strings instead of const char*s? If so I would be happy to do the legwork and submit a patch. Thanks, -Gabe

6 16

Reg : Boost Error - any.hpp
by Vijay 27 Aug '11

27 Aug '11

Hi, We are using boost version 1.31.0 in our C++ code. Our OS is HP-UX 11.31 Itanium. We use aCC compiler. While compiling my code, I'm getting the below error. Can any one help me to fix this issue ? "/opt/app/q1app2c4/boost-1.31.0/boost/any.hpp", line 125: error #2070: incomplete type is not allowed ValueType held; ^ detected during: instantiation of class "boost::any::holder<ValueType> [with ValueType=Fcif]" at line 32 instantiation of "boost::any::any(const ValueType &) [with ValueType=Fcif]" at line 35 of "/opt/app/q1app2c4/src/share/incl/Fcif.h" Cheers, Vijay....(V2K) E-mail to : v2k.sweet(a)gmail.com Catch me @ 9962003328, 7871181610 Blackberry PIN : 259943F3 "Life is just one grand sweet song, so start the music."

2 1

accumulator serializable?
by Neal Becker 26 Aug '11

26 Aug '11

I have typedef accumulator_set<el_t,stats<tag::mean,tag::abs_sqr> > accum_t; What would I need to do to serialize an accum_t object?

2 1

[review] Conversion review continues through 8/29
by Gordon Woodhull 26 Aug '11

26 Aug '11

Folks, The review of Vicente Botet Escriba's Conversion library continues through this Monday. So far discussion has been light and there have been only a couple of reviews. I'll attempt to provoke some discussion by offering my own review and by bringing in some opinions made off-list. Your input would be greatly appreciated. Thanks, Gordon

1 0

[Containers] Marshalling deques
by Brian Wood 26 Aug '11

26 Aug '11

There's a thread here -- http://groups.google.com/group/comp.lang.c++/browse_thread/thread/0a6a19f83… that I'd like to mention. Does the deque in the Containers library have support for accessing the chunks it uses? Would you be willing to add a function that gives that? Tia. Shalom, Brian Wood Ebenezer Enterprises http://webEbenezer.net

3 3

Subject: Re: [Boost-users] [Containers] Marshalling deques
by Brian Wood 26 Aug '11

26 Aug '11

Michael Goldshteyn: > I think that having a ?configurable? deque class template > is one of the best things that could be offered by a boost > Containers library. I have always wondered why noone > wrote a version of the deque class template that allowed > the configuration of such things as the page / block size, > rather than have it be determined by a compile time > formula based on the size of the data type being stored. > It would seem to me that the page / block size is one of > the more critical pieces affecting the size / speed > tradeoffs in a deque?s performance when there are many > insertions taking place. The thread I mentioned has a link to a segmented_array container which may be of interest. I agree that what you suggest would be an improvement. Shalom, Brian Wood Ebenezer Enterprises http://webEbenezer.net <http://webebenezer.net/>

1 0

Lighweight header-only version of Boost.Filesystem?
by Mathias Gaunard 25 Aug '11

25 Aug '11

I use Boost.Filesystem in a C++ "script": I use C++ instead of Python or shell script in order to be portable across operating systems. That script is used in bootstrapping the build system of my C++ project, and people have complained that they need to build boost.filesystem just to be able to bootstrap the project. This is made worse by the fact than the rest of my C++ project requires very recent versions of Boost headers and the fact that the ABI of filesystem has changed relatively recently. I had instances of people having problems because they were linking old versions of the filesystem library but using recent filesystem headers. They had a lot of trouble compiling the correct versions of filesystem themselves. I would also like to ship the script at installation time. To do that I statically link filesystem to reduce dependencies. My pretty trivial program, however, is more than 650kB in release mode after stripping (2.2 MB before stripping). All it does is walk a directory recursively and create a few files. I think this is too big. Therefore, I would really like it if there was a lightweight header-only version of Boost.Filesystem. I don't need the full extent of features; I just need to have the ability to do the following portably: - read all files of a directory - create directories - remove files and directories - rename files and directories The first point being the most important.

8 11

[msm]intarnal_transition_table's behavior
by Takatoshi Kondo 25 Aug '11

25 Aug '11

Hello, When I was trying to answer an another thread, I encountered strange behavior. (Re: [boost] [msm]exit pseudo state and event) See 18_InternalTransitionTableTest.cpp. (attached file) I believe that internal_transition_table should work correctly without transition_table. Here is internal_transition_table. // Internal Transition table struct internal_transition_table : mpl::vector< // Event Action Guard msmf::Internal < Event1, Action1_1 ,Guard1_1 > > {}; But Event1 isn't dispatched. I don't understand why. When I add transition_table that includes the Event1, internal_transition_table works correctly. #if 1 // Why is it needed? // Transition table struct transition_table:mpl::vector< // Start Event Next Action Guard msmf::Row < State1_1, Event1, State1_2, msmf::none, msmf::none > // OK // msmf::Row < State1_1, Event2, State1_2, msmf::none, msmf::none > // NG > {}; #endif But if transition_table don't have Event1, internal_transition_table doesn't work correctly. msmf::Row < State1_1, Event2, State1_2, msmf::none, msmf::none > // NG I suspect it is bug. How do you think? Thanks, Takatoshi

3 6