December 2012 - Boost-users

BOOST::ASIO load key.pem with passphrase
by Alvaro Leiva 20 Dec '12

20 Dec '12

Currently I'm working with this: ... ctx.use_certificate_chain_file("./C/cert.pem"); ctx.use_private_key_file("./C/key.pem", boost::asio::ssl::context::pem); ctx.load_verify_file("./C/ca.pem");... So far everything works perfect, but what I really need to do is load the same key.pem but with a passphrase, Looking at asio docs found ssl::context::set_password_callback<http://www.boost.org/doc/libs/1_52_0/doc/html/boost_asio/reference/ssl__con…> wich according to the info calls SSL_CTX_set_default_passwd_cb<http://www.openssl.org/docs/ssl/SSL_CTX_set_default_passwd_cb.html> and allows to handle encrypted PEM files, please remember that I'm much more familiarized with high level languages like python, so c++ is not my forte any help is appreciated, Thank you ! -- Alvaro Leiva

1 0

Link problem on Mac - tag_original_exception_type
by John M. Dlugosz 20 Dec '12

20 Dec '12

I'm getting a linker error when I build my program on the Mac, that __ZTSPN5boost27tag_original_exception_typeE is duplicate defined. This is the only symbol that is giving this problem. Any ideas what's special about that one, or what it might be?

1 0

[preprocessor]:issues with expansion.
by Littlefield, Tyler 20 Dec '12

20 Dec '12

hello all: I have the following code: #define REGISTER_MODULE(module)(\ #ifdef BOOST_PP_EQUAL(BOOST_PP_LIST_SIZE(MODULES), 0)\ //there are currently no modules in the list. #define MODULES((module), BOOST_PP_NIL) #else BOOST_PP_LIST_APPEND(MODULES, module)\ #endif ) I am somewhat of a newb at preprocessor magic, so any advice would be useful. For whatever reason this translates out to 'module)' when I try to compile it with -E -P. The idea is that it will add to the modules list (assuming the modules list exists) the module to be registered, which should just be a type. Thanks, -- Take care, Ty http://tds-solutions.net The aspen project: a barebones light-weight mud engine: http://code.google.com/p/aspenmud He that will not reason is a bigot; he that cannot reason is a fool; he that dares not reason is a slave.

3 3

C++ gurus - really dumb question regarding partial speciallization.
by Robert Ramey 20 Dec '12

20 Dec '12

I've got the following code which fails to compile. I'm really stumped by this. I've consulted the standard document on the subject and for the life of me I can't see anything wrong with it. It fails with the same message on vc 9.0 as well as gcc 4.5.3. It's so simple it can't be a compiler issue. I appoligize in advance for spaming the list here - but I'm really, really stuck. Robert Ramey // primary template template< class T, int MIN, int MAX > struct safe_range1{}; // instantiate primary as a test safe_range1<int, 0, 1> t1; // partial specialization # 1 template< int MIN, int MAX > struct safe_range1<int, MIN, MAX>{}; // instantiate partial specialization - what the ??? // fails with "too few template parameters" !!! safe_range1<0, 1> t2; // partial specialization # 2 template<class T> struct safe_range1<T, 0, 1> {}; // also fails with "too few template parameters" !!! safe_range1<int> t3;

3 3

[polygon] bug with self intersecting polygons ?
by Renaud Lepère 20 Dec '12

20 Dec '12

Hello, I'm trying to remove some internal loops on polygons as illustrated in the following drawing : +---------------+ +---------------+ | | / | / | |\ / | / | | X | X | |/ \ | \ | / \ | \ +----->---------+ +----->---------+ I need strong numerical robustness, i am using boost polyon with integer coordinates (using boost-1.52 + win32). It works on a lot of samples but i encounter a bug on an example. I reduced to the following sample which is roughtly a triangle (IMHO it should return a triangle). #include <boost/polygon/polygon.hpp> #include <vector> #include <iostream> using namespace boost::polygon; using namespace std; typedef point_data< int > point; typedef vector< point > points; typedef polygon_set_data< int > polygon_set; typedef polygon_with_holes_data< int > polygon_with_holes; typedef vector< polygon_with_holes > polygons_with_holes; /* * A triangle A, B, C with some nearly aligned points between B and C. * * A * + * |\ * | \ * | \ * | \ * | \ * | \ * | \ * | \ * | /-+ C * B +--- */ polygon_with_holes MakeRawPolygon() { points ps; ps.push_back(point(-181928106,288346744)); // A ps.push_back(point(-15311797,-289428209)); // B ps.push_back(point(56093690,-270295166)); ps.push_back(point(24502047,-278760121)); ps.push_back(point(57745146,-269852659)); ps.push_back(point(56791908,-270108078)); ps.push_back(point(-14613579,-289241121)); ps.push_back(point(82923673,-263106094)); // C polygon_with_holes poly; set_points(poly, ps.begin(), ps.end()); return poly; } int main() { polygon_with_holes polygon(MakeRawPolygon()); polygon_set ps; ps.insert(polygon); // first unrool polygons_with_holes unrolled_polygons; ps.get(unrolled_polygons); if (unrolled_polygons.size() == 0u) { std::cout << "error" << endl; } } Is there something wrong in my code ? or is this a real bug. Thanks for your help and time. Renaud

1 0

[Boost.Test] Command line arguments
by Noah Roberts 19 Dec '12

19 Dec '12

I want to add command line arguments to my unit test but I cannot find how to do so. I found the place to get argc and argv from the main suite, but when I pass in arguments that the framework doesn't already know about I get heap corruption. Is there a way to instruct the unit test framework about additional command line arguments you want to process in your test?

2 1

Boost.MSM -> Ignore events that were not explicitly defined for a state
by RaRi 19 Dec '12

19 Dec '12

Hello list, I'm experimenting a bit with *boost.msm* from the *boost 1.52* library. Please consider the following small code snippted which generally defines a state machine with the states *State1*, *State2* and *State3*, and the events *Event1* (triggers the transition from State1 to State2) and *Event2* (triggers the transition from State2 to State3): #include <iostream> #include <boost/msm/back/state_machine.hpp> #include <boost/msm/front/state_machine_def.hpp> #include <boost/msm/front/functor_row.hpp> namespace { namespace msm = boost::msm; namespace msmf = boost::msm::front; namespace mpl = boost::mpl; // ----- Events struct Event1 {}; struct Event2 {}; // ----- State machine struct Sm1_:msmf::state_machine_def<Sm1_> { // States struct Init:msmf::state<> {}; struct State1:msmf::state<> { // Entry action template <class Event,class Fsm> void on_entry(Event const&, Fsm&) { std::cout << "State1::on_entry()" << std::endl; } // Exit action template <class Event,class Fsm> void on_exit(Event const&, Fsm&) { std::cout << "State1::on_exit()" << std::endl; } }; struct State2:msmf::state<> { // Entry action template <class Event,class Fsm> void on_entry(Event const&, Fsm&) { std::cout << "State2::on_entry()" << std::endl; } // Exit action template <class Event,class Fsm> void on_exit(Event const&, Fsm&) { std::cout << "State2::on_exit()" << std::endl; } }; struct State3:msmf::state<> { // Entry action template <class Event,class Fsm> void on_entry(Event const&, Fsm&) { std::cout << "State3::on_entry()" << std::endl; } // Exit action template <class Event,class Fsm> void on_exit(Event const&, Fsm&) { std::cout << "State3::on_exit()" << std::endl; } }; // Set initial state typedef State1 initial_state; // Actions struct InitAction { template <class Event, class Fsm, class SourceState, class TargetState> void operator()(Event const&, Fsm&, SourceState&, TargetState&) const { std::cout << "InitAction()" << std::endl; } }; struct transition_table:mpl::vector< // Start Event Next Action Guard msmf::Row < State1, Event1, State2, msmf::none, msmf::none >, msmf::Row < State2, Event2, State3, msmf::none, msmf::none > > {}; }; // Pick a back-end typedef msm::back::state_machine<Sm1_> Sm1; void test() { Sm1 sm1; sm1.start(); std::cout << "> Send Event2" << std::endl; sm1.process_event(Event2()); std::cout << "> Send Event1" << std::endl; sm1.process_event(Event1()); } } int main() { test(); return 0; } If I compile and execute the code above the software crashes due to the fact, that *Event2* is received in the state *State1*. My understanding of a state machine and boost.msm was, that all events which are not defined for a particular state, will be just ignored and the state receiving this unknown event (here *Event2*) will keept. Is there a possibility in boost.msm ( maybe by adopting to the transition table) to stay in the current state if an event was received which was not assigned to this state? Thank you in advance! Best regards, RaRi -- View this message in context: http://boost.2283326.n4.nabble.com/Boost-MSM-Ignore-events-that-were-not-ex… Sent from the Boost - Users mailing list archive at Nabble.com.

2 4

[MPL] HAS_XXX gives the wrong answer after "enable_if" on incomplete type in GCC 4.6/7
by Duncan Exon Smith 19 Dec '12

19 Dec '12

I've run into an unexpected behaviour, and I'm not sure if the compiler has a bug, if Boost.MPL has a bug, or if I have the wrong expectations. I am using Boost v1.49.0, but I also tested r82084 of the Boost trunk. In particular, I have: BOOST_MPL_HAS_XXX_TRAIT_DEF(trait) // skipping important code here struct traitor_1 { typedef void *trait; }; struct traitor_2 { typedef void *trait; }; static_assert(has_trait<traitor_1>::value, "traitor_1::trait is missing"); static_assert(has_trait<traitor_2>::value, "traitor_2::trait is missing"); and the compiler tells me that "has_trait<traitor_1>::value" is "false", while "has_trait<traitor_2>::value" is "true". The above listing skips some key code involving boost::enable_if that appears to break "has_trait". The full listing is below. I would appreciate if any experts could tell me if this behaviour is expected. The complete code listing is below. I've tried: g++-4.6 -std=gnu++0x -I/usr/include/boost-1_49 -c -o/dev/null traitor.cpp g++-4.7 -std=gnu++0x -I/usr/include/boost-1_49 -c -o/dev/null traitor.cpp Thanks very much, Duncan // traitor.cpp # include <boost/utility/enable_if.hpp> # include <boost/mpl/has_xxx.hpp> BOOST_MPL_HAS_XXX_TRAIT_DEF(trait) class C { struct enabler { }; public: template <class T> C(const T &, typename boost::enable_if<has_trait<T>, enabler>::type = enabler()); }; struct traitor_1; void g(const C &); void g(const traitor_1 &); void f(const traitor_1 &t1) { g(t1); } struct traitor_1 { typedef void *trait; }; struct traitor_2 { typedef void *trait; }; static_assert(has_trait<traitor_1>::value, "traitor_1::trait is missing"); static_assert(has_trait<traitor_2>::value, "traitor_2::trait is missing");

3 4

[Getting Started] Library Naming section is out of date
by Colin Powers 19 Dec '12

19 Dec '12

Hi all, apologies for any bad form in this email as it's my first posting, The getting started guide (current link: http://www.boost.org/doc/libs/1_52_0/more/getting_started/unix-variants.htm… ) states "Libraries built without multithreading support can be identified by the absence of -mt". However having done a bit of googling around I think this is no longer true, at least not necessarily. It seems the naming convention changed around Boost 1.40 and this documentation has never been updated. Here are some Stack Overflow links that suggest as much: http://stackoverflow.com/questions/1768943/building-boost-on-linux-library-… http://stackoverflow.com/questions/8940249/boost-how-bjam-constructs-a-libr… http://stackoverflow.com/questions/2293962/boost-libraries-in-multithreadin… I have also done a bit of a play around building Boost 1.49 and confirmed this seems to be the case. Should the wording in the getting started guide be redone to make this clear? It worried me for a moment when I thought I had not been using multithreaded libraries because there was no -mt in the filenames. Cheers -Colin

1 0

[xpressive] compiler errors in c++11 mode with trunk
by Nathan Ridge 18 Dec '12

18 Dec '12

Hello, The following code: #include <string> #include <boost/xpressive/xpressive_static.hpp> void foo(const boost::xpressive::sregex& regex) { std::string input; boost::xpressive::regex_replace(input, regex, ""); } when compiled with GCC (I tested with 4.6/4.7/4.8) in C++11 mode, gives the following compiler error: In file included from boost/boost/xpressive/detail/core/regex_impl.hpp:21:0, from boost/boost/xpressive/match_results.hpp:54, from boost/boost/xpressive/detail/core/access.hpp:21, from boost/boost/xpressive/detail/core/state.hpp:18, from boost/boost/xpressive/detail/core/matcher/alternate_end_matcher.hpp:20, from boost/boost/xpressive/detail/core/matchers.hpp:17, from boost/boost/xpressive/regex_primitives.hpp:22, from boost/boost/xpressive/xpressive_static.hpp:24, from test.cpp:2: boost/boost/xpressive/detail/utility/tracking_ptr.hpp: In instantiation of 'struct boost::xpressive::detail::tracking_ptr<boost::xpressive::detail::regex_impl<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> > > >': boost/boost/proto/detail/preprocessed/expr_variadic.hpp:50:49: required from 'struct boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::xpressive::detail::tracking_ptr<boost::xpressive::detail::regex_impl<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> > > > >, 0l>' boost/boost/xpressive/basic_regex.hpp:53:8: required from 'struct boost::xpressive::basic_regex<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> > >' boost/boost/xpressive/regex_algorithms.hpp:916:5: required from 'BidiContainer boost::xpressive::regex_replace(BidiContainer&, const boost::xpressive::basic_regex<BidiIter>&, const typename boost::iterator_value<BidiIter>::type*, boost::xpressive::regex_constants::match_flag_type, typename boost::disable_if<boost::xpressive::detail::is_char_ptr<BidiRange> >::type*) [with BidiContainer = std::basic_string<char>; BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >; typename boost::iterator_value<BidiIter>::type = char; typename boost::disable_if<boost::xpressive::detail::is_char_ptr<BidiRange> >::type = void]' test.cpp:7:53: required from here boost/boost/xpressive/detail/utility/tracking_ptr.hpp:440:73: error: no type named 'unspecified_bool_type' in 'class boost::intrusive_ptr<boost::xpressive::detail::regex_impl<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> > > >' It works fine if I don't compile in C++11 mode. It used to work fine even in C++11 mode in the 1.51 release (don't have 1.52 around to test ATM). Any suggestions for a fix/workaround? Thanks, Nate

2 2