March 2015 - Boost-users - lists.preview.boost.org

try_numeric_convert (akin to try_lexical_convert)
by Chris Franz 23 Mar '15

23 Mar '15

We're using the new try_lexical_convert function in our code so we can encapsulate errors in the standard manner used in our project. A counterpart for numeric_cast would be useful. Is any such thing in the works?

2 1

Re: [Boost-users] [range] functor defined result_type with no &, causing temporary variable warnings on VS
by Nick Stokes 23 Mar '15

23 Mar '15

This question is a followup from a multi_index discussion at http://lists.boost.org/boost-users/2015/03/84028.php. Joaquin explained the situation very accurately, so I am including his explanation following my summary below for context (I hope this does not constitute top posting :) In summary the problem is: struct Foo { int i; } struct GetIntMem { typedef int result_type; const int& operator()(const Foo& f) const { return f.i ; } }; aFooRange | boost::adaptors::transformed( GetIntMem() ); yields "warning C4172: returning address of local variable or temporary" in VS 2012 and 2013, with Boost 1.49. There is no warning with Boost 1.56. Is this construct safe with Boost 1.49? In the context of multi_index, the key extractor type is the "GetIntMem". Please see below for details. On Fri, Mar 20, 2015 at 5:33 AM, Joaquin M Lopez Munoz <joaquin(a)tid.es> wrote: > > Please don't top-post: > > http://www.boost.org/community/policy.html#quoting > > Sure. Sorry. Thanks for the link, useful info. > So, to sum up the top-posted chain of posts of yours, > boost::multi_index::member<Class,Type,PtrToMember> publicizes its > result type as > > typedef Type result_type; > > yet its call operator overloads return Type& or const Ttype&, and this > results in some warnings in VS 12 / Boost 1.49 when used in combination > with boost::adaptors::transform. > > So, whatever the problem is, it does not belong in Boost.MultiIndex, > since member merely defines result_type in accordance with the > requirements of the Key Extractor model: > > http://www.boost.org/libs/multi_index/doc/reference/ > key_extraction.html#key_extractors > > I mean, defining result_type in whatever way (or not defining it > at all) is not an error per se; it is Boost.Range assumptions on > this typedef that might be problematic. Unfortunately, the documentation > for boost::adaptors::tranform(rng,fun) > > http://www.boost.org/libs/range/doc/html/range/reference/ > adaptors/reference/transformed.html > > do not mention what the requirements on fun are, whether it is > mandatory that a result_type be present and how this is handled by > Boost.Range. I suggest you initiate a new discussion with [range] > in the subject line showing the problem you found. I suspect this > is related to boost:result_of > > http://www.boost.org/libs/utility/utility.htm#result_of > > which Boost.Range seems to use internally, but only the author can > tell. Also, if the problem does not show in Boost 1.56 you might be > encouraged to simply upgrade and move on. > > Thanks Joaquin. I could not describe the problem any better than what you have above, so I hope you don't mind that I re-purposed this thread. The question is possibly is rather moot at this point, as the issue does not manifest in Boost 1.56 (possibly earlier). However, it'd be interesting to understand why, and at least make sure using 1.49 this way is safe (I am stuck with that version for the time being). Thanks very much if you followed along this far, and sorry as I fear this post ended up more convoluted that it needs to be :P Nick

1 0

Re: [Boost-users] [asio] wrap lambda async_receive call
by Cheng Mo 23 Mar '15

23 Mar '15

Hi Gavin: >Having said this, using lambdas can get tricky in real-world code, as >it's common to want to start the same read operation when the first >completes, and so on. Just like you said, will the code build a lambda expression when async_read() invoked ? So that "[=](const error_code& ec, size_t count" will be built servial times, it is kind of lavish for contructing the lambda expression, isn't ? It's better that build a function object in static. What do you think ? Cheers~ Cheer~ 程墨 PBI―北京加维通讯电子技术有限公司地址：北京市海淀区西北旺镇丰智东路3号院邮编：100094 Mail: mcheng(a)pbicn.com

2 1

New Iterator Concepts deprecated?
by Peter Johansson 22 Mar '15

22 Mar '15

Hi boosters, I've been looking into the New Iterator Concepts http://www.boost.org/doc/libs/1_57_0/libs/iterator/doc/new-iter-concepts.ht… and then I found this comment on boost trac https://svn.boost.org/trac/boost/ticket/1296 where dave seven years ago wrote: "/the new categories are a dead-end as the standard has lifted the reference requirement on forward iterators, so I don't plan to implement anything like this. I actually plan to deprecate the new categories./" This was seven years ago and I can't see anything about that the concepts have been deprecated, so I just wonder if this statement still holds or did the standard take back the reference requirement? Cheers, -- Peter Johansson

3 2

Boost.Locale Examples doesn't runs in VS2010
by Sarvagya Pant 22 Mar '15

22 Mar '15

I have been trying to learn Boost.Locale Module. Consider http://www.boost.org/doc/libs/1_55_0/libs/locale/doc/html/conversions_8cpp-… example. The code gets successfully compiled but when I try to run it, it gives the error Unhandled exception at 0x74d34b32 in LearningCPP.exe: Microsoft C++ exception: std::bad_cast at memory location 0x00a6fa48.. I have attached the stack-trace of the program also. Here it is: KernelBase.dll!74d34b32() [Frames below may be incorrect and/or missing, no symbols loaded for KernelBase.dll] KernelBase.dll!74d34b32() > msvcr100d.dll!_nh_malloc_dbg(unsigned int nSize, int nhFlag, int nBlockUse, const char * szFileName, int nLine) Line 302 + 0x1d bytes C++ msvcr100d.dll!malloc(unsigned int nSize) Line 56 + 0x15 bytes C++ LearningCPP.exe!std::use_facet<boost::locale::converter<char> >(const std::locale & _Loc) Line 526 C++ LearningCPP.exe!boost::locale::to_upper<char>(const char * str, const std::locale & loc) Line 225 + 0x9 bytes C++ LearningCPP.exe!main() Line 170 + 0xc4 bytes C++ LearningCPP.exe!__tmainCRTStartup() Line 555 + 0x19 bytes C LearningCPP.exe!mainCRTStartup() Line 371 C kernel32.dll!75268543() ntdll.dll!776bac69() ntdll.dll!776bac3c() Did anyone faced this issue when using Boost.Locale in Visual Studio 2010? If so, how do I resolve this issue? *PS:* I have used option Use Unicode Character Set under the Character Set option of Visual Studio. I believe the libraries are correctly linked too. -- *sarvagya*

1 0

boost::property_tree::ptree with write_xml
by Uthpal Urubail 21 Mar '15

21 Mar '15

All, I am looking got the help with xml writer using property tree. My requirement is to write a user defined comment (in below example /*comment*/) in every line of XML file. Example: /*comment*/<debug> /*comment*/ <filename>debug.log</filename> /*comment*/ <modules> /*comment*/ <module>Finance</module> /*comment*/ <module>Admin</module> /*comment*/ <module>HR</module> /*comment*/ </modules> /*comment*/ <level>2</level> /*comment*/</debug> Can someone help me in solving the above? Any help on this would be highly appreciated. boost::property_tree::xml_writer_settings<std::string> w(' ', 4); write_xml(os, pt,w); Regards, UJ

3 4

phoenix 1.55 no-arg mem function fails
by MM 20 Mar '15

20 Mar '15

#include <boost/phoenix/phoenix.hpp> struct Foo { const int& bar() const { return i; } int i; }; int main() { Foo f; const int& ir = boost::phoenix::bind(&Foo::bar, f)(); } The above fails to compile. linux g++492 -std=c++11 -c 1.cpp When bar() has a single int arg for e.g., boost::phoenix::bind(&Foo::bar, f, 5)(); succeeds. The error: In file included from /usr/include/boost/phoenix/bind/bind_member_variable.hpp:13:0, from /usr/include/boost/phoenix/bind.hpp:17, from /usr/include/boost/phoenix/phoenix.hpp:17, from 1.cpp:1: /usr/include/boost/phoenix/bind/detail/member_variable.hpp: In instantiation of ‘struct boost::phoenix::detail::member_variable<const int&() const, const int& (Foo::*)() const>’: /usr/include/boost/proto/make_expr.hpp:77:16: required from ‘struct boost::proto::detail::protoify<boost::phoenix::detail::member_variable<const int&() const, const int& (Foo::*)() const>, boost::proto::domainns_::basic_default_domain>’ /usr/include/boost/proto/detail/preprocessed/make_expr_.hpp:70:9: required from ‘struct boost::proto::detail::make_expr_<boost::phoenix::detail::tag::function_eval, boost::proto::domainns_::basic_default_domain, boost::phoenix::detail::member_variable<const int&() const, const int& (Foo::*)() const>, Foo, void, void, void, void, void, void, void, void, void>’ /usr/include/boost/proto/make_expr.hpp:185:13: required from ‘struct boost::proto::result_of::make_expr<boost::phoenix::detail::tag::function_eval, boost::proto::domainns_::basic_default_domain, boost::phoenix::detail::member_variable<const int&() const, const int& (Foo::*)() const>, Foo, void, void, void, void, void, void, void, void, void>’ /usr/include/boost/phoenix/core/preprocessed/expression_10.hpp:84:13: required from ‘struct boost::phoenix::expr_ext<boost::phoenix::actor, boost::phoenix::detail::tag::function_eval, boost::phoenix::detail::member_variable<const int&() const, const int& (Foo::*)() const>, Foo, void, void, void, void, void, void, void, void, void>’ /usr/include/boost/phoenix/core/preprocessed/expression_10.hpp:24:12: required from ‘struct boost::phoenix::expr<boost::phoenix::detail::tag::function_eval, boost::phoenix::detail::member_variable<const int&() const, const int& (Foo::*)() const>, Foo, void, void, void, void, void, void, void, void, void>’ /usr/include/boost/phoenix/core/detail/preprocessed/function_eval_10.hpp:7:561: required from ‘struct boost::phoenix::detail::expression::function_eval<boost::phoenix::detail::member_variable<const int&() const, const int& (Foo::*)() const>, Foo, void, void, void, void, void, void, void, void, void>’ /usr/include/boost/phoenix/bind/bind_member_variable.hpp:37:5: required by substitution of ‘template<class RT, class ClassT> const typename boost::phoenix::detail::expression::function_eval<boost::phoenix::detail::member_variable<RT, RT ClassT::*>, ClassT>::type boost::phoenix::bind(RT ClassT::*, ClassT&) [with RT = const int&() const; ClassT = Foo]’ 1.cpp:11:52: required from here /usr/include/boost/phoenix/bind/detail/member_variable.hpp:50:17: error: forming reference to qualified function type ‘const int&() const’ RT& operator()(Class& obj) const ^ /usr/include/boost/phoenix/bind/detail/member_variable.hpp:59:23: error: forming reference to qualified function type ‘const int&() const’ RT const& operator()(Class const& obj) const ^ /usr/include/boost/phoenix/bind/detail/member_variable.hpp:68:17: error: forming reference to qualified function type ‘const int&() const’ RT& operator()(Class* obj) const ^ /usr/include/boost/phoenix/bind/detail/member_variable.hpp:74:23: error: forming reference to qualified function type ‘const int&() const’ RT const& operator()(Class const* obj) const Rds,

1 0

phoenix: c++11
by MM 20 Mar '15

20 Mar '15

Hello Are there plans to add emplace_back to the stl part of phoenix? MM

1 0

what happens between "fixed in development" and "available in release"?
by oswin krause 20 Mar '15

20 Mar '15

Hi, Question is in the subject. What has to happen after a fix of a bug in development stage before it enters an official release? Do not get me wrong, I like boost and all it does for the community and all the effort people put into it. And i really would like to help to speed up certain...processes, but for this i have to know what can block this step? Apparently a bug in serialisation - which totally breaks my software to the point where it can not be compiled on several linux distributions und MacOsX since release of boost 1.56 - is fixed in development even prior to 1.57 and is still not available in 1.58. And what I hear from several mails across the mailing list, this is not the only change that got stuck. And somehow i have the feeling that the new boost release cycle won't make the situation any better. As I said, do not get me wrong, but this situation becomes unbearable as these boost versions spread more and more through the ecosystem and there is really nothing on my side I can do about it, except rolling my own implementation and maintaining it, until this whole thing is faded out of all major distributions(you might already get the feeling that I am not really happy about doing that). if there is something i can do to help, I will do it. But I now know that "report bugs and investigate possible fixes and send patches" does not necessarily lead to a fast fix and i am pretty frustrated by the situation. Best, Oswin

8 17

[multi_index] iterating over keys and "extracting" key extractors
by Nick Stokes 20 Mar '15

20 Mar '15

Q1: Is there a builtin in way in MI to iterate over keys rather than elements? I.e. the iterator's value type will be that of the key, not the element. Q2: Is there a way to obtain the type of key extractors given a multi index container? (it is related to Q1, as this sort of a thing could be passed to boost::transform iterator to obtain an alternative answer for Q1) An example is in order: struct Foo { int id; sting name; }; using namespace boost::multi_index; typedef multi_index_container< Foo, indexed_by< ordered_unique< member< Foo, int, &Foo::id > >, ordered_unique< member< Foo, string, &Foo::name > > > MFoo; MFoo foos; // .. populate // Now, we want to iterate over sorted name's only, for e.g: auto beg = answer_to_Q1(foos).begin(); auto end = answer_to_Q1(foos).end(); std::copy( beg, end, ostream_iterator<string>(cout, " ") ); // Continuing the example for Q2: auto aFunctorThatExtractsFooName = answer_to_Q2<M>::type(); auto beg = make_transform_iterator( M.get<1>.cbegin(), aFunctorThatExtractsFooName ); auto end = make_transform_iterator( M.get<1>.cend(), aFunctorThatExtractsFooName ); std::copy( beg, end, ostream_iterator<string>(cout, " ") ); Thanks! Nick

2 6