May 2012 - Boost-users - lists.preview.boost.org

Why does the fusion::set repeated keys?
by niXman 27 May '12

27 May '12

Hi, In this simple code, I expect that the size of the fusion::set is equal to one, because keys are the same. Why the size is equal to two? #include <boost/fusion/container/set.hpp> #include <boost/fusion/include/set.hpp> #include <boost/fusion/container/set/set_fwd.hpp> #include <boost/fusion/include/set_fwd.hpp> #include <boost/fusion/sequence/intrinsic/size.hpp> #include <boost/fusion/include/size.hpp> #include <iostream> int main() { typedef boost::fusion::set<int, int> set1; set1 s1; std::cout << "size1 = " << boost::fusion::result_of::size<set1>::type::value << ", size2 = " << boost::fusion::size(s1) << std::endl; } http://liveworkspace.org/code/166b54cdd208f7b252bf1f38a1a6ec4b Thanks! -- Regards, niXman ___________________________________________________ Dual-target(i686/x86_64) MinGW compiler for i686/x86_64 hosts: http://sourceforge.net/projects/mingwbuilds/

2 1

[asio] Boost asio mailing list
by Edward Diener 27 May '12

27 May '12

How do I subscribe to the asio mailing list ?

2 1

BOOST_RESULT_OF_USE_DECLTYPE and Boost.Optional ?
by John M. Dlugosz 27 May '12

27 May '12

Hmm, the error isn't quite what I said: 1>V:\Trunk\stable\src\Include\Tools/async.h(268): error C2664: 'boost::unique_future<R>::unique_future(boost::unique_future<R> &)' : cannot convert parameter 1 from 'boost::unique_future<R>' to 'boost::unique_future<R> &' 1> with 1> [ 1> R=boost::optional<in_addr> & 1> ] 1> and 1> [ 1> R=boost::optional<in_addr> 1> ] 1> and 1> [ 1> R=boost::optional<in_addr> & 1> ] But my other test cases of using unique_future (with simple types) work OK. —John

1 0

udp client
by Christer Borgqvist 27 May '12

27 May '12

Hi, I use the HTTP server 3 example, i want to dump all the request and response to a thread queue and using a udp client to send to syslog, how should i do that. / Christer

1 1

logger progress?
by Victor Whiskey Yankee 26 May '12

26 May '12

Hello, How is the boost logger going for proper inclusion? Thanks, Vic

2 1

Apple "Block" closures and boost::function
by John M. Dlugosz 26 May '12

26 May '12

I'm looking at using Apple's proprietary closure blocks as a substitute for C++ lambda functions on a project that needs to be portable between Mac (LLVM 3.1, but not using the C++0x dialect compiler switch) and Windows (Visual Studio 10). The project uses Boost.TR1 to supply std::tr1::function and related stuff on the Mac build. Now I found that the compiler handles the nonstandard block objects in Functor-like template situations in a manner perfectly analogous to C-style pointers to functions. I can even assign one to a boost::function with no complaint! The only issue seems to be that it never calls Block_copy/Block_release. So it works OK for passing them to STL algorithms that uses them on the spot, but will probably do bad things if used in general. Does anybody have something ready-made, to efficiently add the copy/destroy semantics to functors that hold such "blocks"? That would be much more efficient than wrapping them in another layer. Or, any pointers to the Boost innerds for doing that myself? Thanks, —John

1 0

[Test] main for BOOST_TEST_DYN_LINK with manual registration
by Rhys Ulerich 25 May '12

25 May '12

What from example 15 from the Boost.Test "Manually registered test suites" documentation[1] needs to change if instead of #include <boost/test/included/unit_test.hpp> one used #define BOOST_TEST_DYN_LINK #include <boost/test/unit_test.hpp> ? >From reading [1] and [2], one needs to provide a main() that invokes the unit_test_main, but I'm at a loss for what it would look like... I don't think I'm running afoul of BOOST_TEST_ALTERNATIVE_INIT_API from reading <boost/test/unit_test.hpp> where the main() definition cares nothing about that #define, but I could be wrong. Help or a known-good example much appreciated, Rhys [1] http://www.boost.org/doc/libs/1_49_0/libs/test/doc/html/utf/user-guide/test… [2] http://www.boost.org/doc/libs/1_49_0/libs/test/doc/html/utf/user-guide/test…

1 2

[container] Compilation failure with clang 3.1
by Alexandre Hamez 25 May '12

25 May '12

Hello, When compiling Boost.Container, clang 3.1 (stable release, Mac OS X 10.7.4) fails: > /opt/local/include/boost/container/allocator/allocator_traits.hpp:167:105: >> error: type name requires a specifier or qualifier > > template <typename T> using rebind_alloc = >> boost::intrusive::detail::type_rebinder<Alloc, T>::type; > > >> ^ > > /opt/local/include/boost/container/allocator/allocator_traits.hpp:167:59: >> error: expected ';' after alias declaration > > template <typename T> using rebind_alloc = >> boost::intrusive::detail::type_rebinder<Alloc, T>::type; > > ^ > > ; > > /opt/local/include/boost/container/allocator/allocator_traits.hpp:168:72: >> error: use of undeclared identifier 'rebind_alloc' > > template <typename T> using rebind_traits = allocator_traits< >> rebind_alloc<T> >; > > ^ > > /opt/local/include/boost/container/allocator/allocator_traits.hpp:168:85: >> error: 'T' does not refer to a value > > template <typename T> using rebind_traits = allocator_traits< >> rebind_alloc<T> >; > > >> ^ > > /opt/local/include/boost/container/allocator/allocator_traits.hpp:168:29: >> note: declared here > > template <typename T> using rebind_traits = allocator_traits< >> rebind_alloc<T> >; > > ^ > > /opt/local/include/boost/container/allocator/allocator_traits.hpp:168:87: >> error: expected ';' after alias declaration > > template <typename T> using rebind_traits = allocator_traits< >> rebind_alloc<T> >; > > However gcc 4.7 has no problem with it. Does anyone has experienced the same thing and possibly found a workaround? Thank you! Alexandre Hamez

2 2

Spirit, StateChart, MSM
by asif saeed 25 May '12

25 May '12

Hi, What are the differences between these three libraries? I feel I can use any of these libs. Is there any page where the comparison/pros&cons are listed and so on? Best regards, Asif

3 2

[msm] Two identical orthogonal regions?
by Aurelian Melinte 25 May '12

25 May '12

Hi, I am trying to put two identical orthogonal regions in a state machine (each region would model a "channel" and I can have multiple such channels). One way I can think of is duplicating the states through typedefs and duplicating entries in the transition table. Is there a way to avoid this duplication? Regards, a.

2 2