- Boost-users - lists.boost.org

Which encryption algorithm is used in Boost::Asio and SSL?
by Andi Clemens 06 Sep '11

06 Sep '11

Hi, I searched the web for some time now, but I was not able to find out which encryption algorithm is used when using SSL with Boost::Asio. Is there a standard algorithm or do the communicating sockets handle out some method? Andi

1 0

[Spirit] compilation problem
by Igor R 06 Sep '11

06 Sep '11

Hello, I've upgraded to 1.47, and any attempt to include a Spirit header produces the following compiler error (MSVC 10): #include <boost/spirit/include/qi.hpp> int main() { } "../spirit/home/support/detail/endian.hpp(22): fatal error C1083: Cannot open include file: 'boost/integer/endian.hpp': No such file or directory" The error is in the following lines: // If Boost has the endian library, use it, otherwise use an adapted version // included with Spirit #if BOOST_VERSION >= 104600 #include <boost/integer/endian.hpp> #else #include <boost/spirit/home/support/detail/integer/endian.hpp> #endif Actually, there's no boost/integer/endian.hpp file in the zip that I've downloaded. What am I doing wrong? Thanks.

1 1

[serialization] boost::serialization adds huge amounts of exports to resultant Windows PE file
by Matheus Peschke de Azevedo 06 Sep '11

06 Sep '11

Chris, Boost serialization defaults lots of classes/functions to be automatically exported. This is done in \boost\serialization\force_include.hpp: #if defined(BOOST_HAS_DECLSPEC) && !defined(__COMO__) # if defined(__BORLANDC__) # define BOOST_DLLEXPORT __export # else # define BOOST_DLLEXPORT __declspec(dllexport) # endif #elif ! defined(_WIN32) && ! defined(_WIN64) # if defined(__MWERKS__) # define BOOST_DLLEXPORT __declspec(dllexport) # elif defined(__GNUC__) && (__GNUC__ >= 3) # define BOOST_USED __attribute__ ((used)) # elif defined(__IBMCPP__) && (__IBMCPP__ >= 1110) # define BOOST_USED __attribute__ ((used)) # elif defined(__INTEL_COMPILER) && (BOOST_INTEL_CXX_VERSION >= 800) # define BOOST_USED __attribute__ ((used)) # endif #endif The easiest workaround for this is: 1. Place your serialization #include lines in a precompiled header. 2. Right after all your boost serialization #includes, write this: #ifdef BOOST_DLLEXPORT #undef BOOST_DLLEXPORT // it was '__declspec(dllexport)' #define BOOST_DLLEXPORT // now it's '' #endif Just rebuild your project and you'll see all exports gone. No need to recompile boost serialization lib as functions affected are templates. Regards, Matheus

1 0

boost bind() error for creating thread
by Jack Bryan 05 Sep '11

05 Sep '11

Hi, I using boost::bind() to create thread. But, I got errors at: threadGroup.create_thread(boost::bind(&lab1::Server::Run, server)); Any help is really appreciated. Code is as follows: --------------------------------------------- class Server {public: // The constructor takes a port number and prepares to receive HTTP // requests from clients on that port. explicit Server(int port); // Closes the connection. ~Server(); // void Run(); //Server(Server&);private: // 'listening' socket used to establish HTTP connections int listen_fd_; // Non-copyable, non-assignable Server(Server&); Server& operator=(Server&);}; int main(int argc, char *argv[]) { if (argc != 2) { std::cout << "Usage: lab1 <port>" << std::endl; return 1; } // Convert the port from a string to an integer. int port_number; std::istringstream port_stream(argv[1]); // argv[1] is port number, port_stream >> port_number; // Convert the thread number from a string to an integer. int thread_number; std::istringstream thread_stream(argv[2]); // argv[1] is port number, thread_stream >> thread_number; lab1::Server server(port_number); boost::thread_group threadGroup; for(int i=0;i<thread_number;i++) { threadGroup.create_thread(boost::bind(&lab1::Server::Run, server)); }threadGroup.join_all(); return 0;} error: no matching function for call to âboost::_bi::bind_t<void, boost::_mfi::mf0<void, lab1::Server>, boost::_bi::list1<boost::_bi::value<lab1::Server> > >::bind_t(boost::_bi::bind_t<void, boost::_mfi::mf0<void, lab1::Server>, boost::_bi::list1<boost::_bi::value<lab1::Server> > >)â /bind.hpp:865: note: candidates are: boost::_bi::bind_t<void, boost::_mfi::mf0<void, lab1::Server>, boost::_bi::list1<boost::_bi::value<lab1::Server> > >::bind_t(boost::_bi::bind_t<void, boost::_mfi::mf0<void, lab1::Server>, boost::_bi::list1<boost::_bi::value<lab1::Server> > >&) lab2.cpp:241: error: initializing argument 1 of âboost::thread* boost::thread_group::create_thread(F) [with F = boost::_bi::bind_t<void, boost::_mfi::mf0<void, lab1::Server>, boost::_bi::list1<boost::_bi::value<lab1::Server> > >]â bind_mf_cc.hpp: In function âboost::_bi::bind_t<R, boost::_mfi::mf0<R, T>, typename boost::_bi::list_av_1<A1>::type> boost::bind(R (T::*)(), A1) [with R = void, T = lab1::Server, A1 = lab1::Server]â error: initializing argument 1 of âboost::thread* boost::thread_group::create_thread(F) [with F = boost::_bi::bind_t<void, boost::_mfi::mf0<void, lab1::Server>, boost::_bi::list1<boost::_bi::value<lab1::Server> > >]â instantiated from herebind_mf_cc.hpp:24: error: no matching function for call to âboost::_bi::list1<boost::_bi::value<lab1::Server> >::list1(boost::_bi::list1<boost::_bi::value<lab1::Server> >)â

2 3

Re: [Boost-users] [boost] [Review] Boost.Endian by BEman Dawes starts today
by Hartmut Kaiser 05 Sep '11

05 Sep '11

> According to the schedule, the review of the Boost.Endian library by Beman > Dawes starts today. > > =========== > What is it? > =========== > > Boost.Endian provides facilities to manipulate the byte ordering of > integers. > > * The primary use case is binary I/O of integers for portable exchange > with other systems, via either file or network transmission. > > * A secondary use case is to minimizing storage size via integers of sizes > and/or alignments not supported by the built-in types. Integers 1, 2, 3, > 4, 5, 6, 7, and 8 bytes in length are supported. > > * Two distinct approaches to byte ordering are provided. Each approach has > a long history of successful use, and each approach has use cases where it > is superior to the other approach. > > * The explicit approach provides explicit functions to reorder bytes. > All four combinations of non-modifying or modifying, and unconditional or > conditional, functions are provided. > > * The implicit approach provides integer classes that mimic the built-in > integers, implicitly handling all byte reordering. Even if this is not a full review, I would like to vote YES to include this library into Boost. Boost.Spirit is using (and shipping) with an older version of this library for several years now and we never had any problems with its usage in Spirit. It is used as the underlying framework for the binary parsers and generators and it is functioning as advertised. As a quick test I replaced the internal (older) version of Boost.Endian in Spirit with the reviewed version. All of Spirits regression tests still pass. Regards Hartmut --------------- http://boost-spirit.com > > =================== > Getting the Library > =================== > > Docs are available at http://boost.cowic.de/rc/endian/doc/index.html > A zip file is available at http://boost.cowic.de/rc/endian/endian-rc1.zip > INSTALL instructions at http://boost.cowic.de/rc/endian/INSTALL > > Alternately, the whole library can be checked out of the sandbox: > > svn co http://svn.boost.org/svn/boost/sandbox/endian endian > > ================ > Writing a Review > ================ > > The reviews and all comments should be submitted to the developers list, > and the email should have "[Endian] Review" at the beginning of the > subject line to make sure it's not missed. > > Please explicitly state in your review whether the library should be > accepted. > > The general review checklist: > > - 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. > > > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Metaprogramming + Multiple Inheritance?
by Hossein Haeri 05 Sep '11

05 Sep '11

Dear all, I am looking for problems a reasonable design for solving which requires mixing (template/preprocessor) metaprogramming and multiple inheritance, say for a single class. In particular, has any part of the Boost library been designed with this mixture? TIA,--Hossein

3 6

[meta-state-machine] Flag_AND doesn't work
by Péter Szabados 05 Sep '11

05 Sep '11

Hi, I am using Boost 1.47.0, and wrote a state machine in MSM with 2 parallel regions. In each region, one state has a flag defined. According to the documentation, when I ask the flag the following way: sm.is_flag_active<FlagStarted, StateMachine::Flag_AND>() then it returns true if both regions are in a state with the flag. However, it doesn't work for me. I have attached an example of this problem. It has the states Stopped1, Started1 and Stopped2, Started2 for the two regions respectively. The states Started1 and Started2 has the flag FlagStarted attached. The flag is checked after each call of process_event. The output of the program is the following: Entering Stopped1 Entering Stopped2 (sm.is_flag_active<FlagStarted, StateMachine::Flag_OR>()): no (sm.is_flag_active<FlagStarted, StateMachine::Flag_AND>()): no Leaving Stopped1 Entering Started1 (sm.is_flag_active<FlagStarted, StateMachine::Flag_OR>()): yes (sm.is_flag_active<FlagStarted, StateMachine::Flag_AND>()): no Leaving Stopped2 Entering Started2 (sm.is_flag_active<FlagStarted, StateMachine::Flag_OR>()): yes (sm.is_flag_active<FlagStarted, StateMachine::Flag_AND>()): no After the second transition, we are in state (Started1, Started2). The flag should be active here, but it isn't. Is there a problem with MSM, or am I doing something wrong? -- Péter

2 1

zip_iterator documentation: probably malformed example
by Krzysztof Żelechowski 05 Sep '11

05 Sep '11

At [http://www.boost.org/doc/libs/1_47_0/libs/iterator/doc/zip_iterator.html Zip Iterator]: is:: {{{zip_it->get<0>() = 42.0;}}} (syntax error) works:: {{{zip_it -> template get <0> () = 42.0;}}}

3 3

exceptions from boost::filesystem not catchable on os/x 10.6.8 boost-1.47.0
by david x callaway 05 Sep '11

05 Sep '11

os/x 10.6.8 uname -a Darwin apple1 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386 boost 1.47.0 ./bootstrap.sh --prefix=$HOME/boost ./b2 link=static --disable-filesystem2 install # I've tried without disabling filesystem2, same result gcc -v Using built-in specs. Target: i686-apple-darwin10 Configured with: /var/tmp/gcc/gcc-5666.3~6/src/configure --disable-checking --enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 --with-gxx-include-dir=/include/c++/4.2.1 Thread model: posix gcc version 4.2.1 (Apple Inc. build 5666) (dot 3) test app compiled: g++ -Wall -I $HOME/boost/include fs.cpp -L$HOME/boost/lib -lboost_filesystem -lboost_system otool -L a.out a.out: /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11) source below. when I run it with a non-existent filename I expect to catch an exception, but instead nothing happens, i.e. I just return to the shell prompt. I tried defining a struct locally and throwing it and the catch works fine. any ideas? thx dxc ------------------------------------------------------------ #include <iostream> #include <stdlib.h> #include "boost/filesystem.hpp" int main(int argc, const char** argv) { if(argc != 2) { std::cout << "usage: a.out filename\n"; exit(1); } const char* a_path = argv[1]; try { boost::filesystem::exists(a_path); } catch(const boost::filesystem::filesystem_error& e) { std::cout << "caught filesystem_error\n"; std::cout << e.what() << "\n"; exit(1); } catch(const std::exception& e) { std::cout << "caught some other error\n"; std::cout << e.what() << "\n"; exit(1); } catch(...) { std::cout << "caught unknown exception\n"; exit(1); } return 0; }

3 3

Using boost function input iterator with class member functions
by Michael King 05 Sep '11

05 Sep '11

Hello, I am trying to use a class member function in conjunction with boost's function input iterator, and am having trouble coming up with a solution which can in any way be considered elegant... My initial thought process was to do something like : std::copy( // does not work because the functor (1st arg to make_function_input iterator ) cannot be temporary... or something like that boost::make_function_input_iterator(boost::bind(&My_Class::my_function, 0)), boost::make_function_input_iterator(boost::bind(&My_Class::my_function, 10)), std::ostream_iterator<result_type>(std::cout, " ") ); However, this fails as noted above. Thus, i had to look at some compiler error messages in order to figure out the return type of boost::bind and create some boost::bind object producing the working code below, however, this looks pretty terrible. Can anyone suggest a more convenient solution to the problem I am trying to solve? Thanks, Michael King #include<iostream> #include<iterator> #include<boost/bind.hpp> #include<boost/iterator/function_input_iterator.hpp> class foo { public: typedef double result_type; result_type return_random() const { return drand48(); } }; int main() { foo bar; // found type from compiler error message... boost::_bi::bind_t< double, boost::_mfi::cmf0< double, foo>, boost::_bi::list1< boost::_bi::value<foo> > > f = boost::bind(&foo::return_random, bar); std::copy( boost::make_function_input_iterator(f, 1), boost::make_function_input_iterator(f, 10), std::ostream_iterator<double>(std::cout, "\n") ); return 0; }

2 1