- Boost-users - lists.boost.org

boost::serialization problem with own defined primitive type
by Robert Bielik 30 May '11

30 May '11

Hi all, I've tried to define operator >> & << in order to make a juce::String serializable in the same manner as a std::wstring. Here is the question thread on StackOverflow: http://stackoverflow.com/questions/6126133/boost-deserialization-problem-of… Any ideas what might be wrong ? Thing is (as I say in the thread above), that it _has_ worked and I obviously have made a change but 2 hours of checking SVN repo diffsets I cannot find it. TIA /Rob

3 8

[range] cannot use lambda predicate in adaptor with certain algorithms
by Nathan Ridge 30 May '11

30 May '11

Hello, I get errors related to lambdas not being default-constructible or copy-assignable when using a lambda as a predicate with certain adaptors (e.g. filtered) and certain algorithms (e.g. min_element). The following code illustrates the problem: #include <boost/range/algorithm/min_element.hpp> #include <boost/range/adaptor/filtered.hpp> int main() { int a[] = {1, 2, 3}; auto is_odd = [](int i){ return i % 2 == 1; }; boost::min_element(a | boost::adaptors::filtered(is_odd)); } The errors are shown below. Is there a workaround for this? Thanks, Nate. Errors: In file included from algorithm:63:0, from /usr/lib/boost/boost/iterator/iterator_concepts.hpp:29, from /usr/lib/boost/boost/range/concepts.hpp:20, from /usr/lib/boost/boost/range/algorithm/min_element.hpp:15, from test.cpp:1: stl_algo.h: In function 'boost::filter_iterator<main()::<lambda(int)>, int *> min_element( boost::filter_iterator<main()::<lambda(int)>, int *> , boost::filter_iterator<main()::<lambda(int)>, int *> )': /usr/lib/boost/boost/range/algorithm/min_element.hpp:44:63: instantiated from 'boost::range_iterator<const T>::ame boost ::range_iterator<const T>::type = boost::filter_iterator< main()::<lambda(int)>, int * > boost::range::min_element( const boost::range_detail::filtered_range< main()::<lambda(int)>, int [3] > & )' test.cpp:8:61: instantiated from here stl_algo.h:6109:4: error: use of deleted function 'boost::filter_iterator< main()::<lambda(int)>, int * > & boost::filter_iterator<main()::<lambda(int)>, int *>::operator=( const boost::filter_iterator<main()::<lambda(int)>, int *> & )' In file included from /usr/lib/boost/boost/range/adaptor/filtered.hpp :16:0, from test.cpp:2: /usr/lib/boost/boost/iterator/filter_iterator.hpp:44:9: error: 'boost ::filter_iterator<main()::<lambda(int)>, int *> & boost::filter_iterator< main()::<lambda(int)>, int * >::operator=( const boost::filter_iterator<main()::<lambda(int)>, int *> & )' is implicitly deleted because the default definition would be ill- formed: /usr/lib/boost/boost/iterator/filter_iterator.hpp:44:9: error: use of deleted function 'main()::<lambda(int)> & main()::<lambda(int)>::operator=( const main()::<lambda(int)> & )' test.cpp:7:20: error: a lambda closure type has a deleted copy assignment operator In file included from /usr/lib/boost/boost/range/adaptor/filtered.hpp :16:0, from test.cpp:2: /usr/lib/boost/boost/iterator/filter_iterator.hpp: In constructor 'boost::filter_iterator<main()::<lambda(int)>, int *>::filter_iterator()': /usr/lib/boost/boost/concept_check.hpp:133:10: instantiated from 'boost::DefaultConstructible< boost::filter_iterator<main()::<lambda(int)>, int *> >::~DefaultConstructible()' /usr/lib/boost/boost/concept/usage.hpp:22:29: instantiated from 'boost::concepts::usage_requirements< boost::DefaultConstructible< boost::filter_iterator<main()::<lambda(int)>, int *> > >::~usage_requirements()' /usr/lib/boost/boost/concept/detail/general.hpp:38:28: instantiated from 'static void boost::concepts::requirement< boost::concepts::failed ************ boost::concepts ::usage_requirements< boost::DefaultConstructible< boost::filter_iterator<main()::<lambda(int)>, int *> > >::************ >::failed()' /usr/lib/boost/boost/concept_check.hpp:132:1: instantiated from 'boost::DefaultConstructible< boost::filter_iterator<main()::<lambda(int)>, int *> >' /usr/lib/boost/boost/range/concepts.hpp:169:16: instantiated from 'boost::range_detail::ForwardIteratorConcept< boost::filter_iterator<main()::<lambda(int)>, int *> >' /usr/lib/boost/boost/concept/detail/has_constraints.hpp:42:5: [ skipping 5 instantiation contexts ] /usr/lib/boost/boost/concept/detail/has_constraints.hpp:42:5: instantiated from 'const bool boost::concepts::not_satisfied< boost::ForwardRangeConcept< const boost::range_detail::filtered_range< main()::<lambda(int)>, int [3] > > >::value' /usr/lib/boost/boost/concept/detail/has_constraints.hpp:45:31: instantiated from 'boost::concepts::not_satisfied< boost::ForwardRangeConcept< const boost::range_detail::filtered_range< main()::<lambda(int)>, int [3] > > >' /usr/lib/boost/boost/mpl/if.hpp:67:11: instantiated from 'boost::mpl ::if_< boost::concepts::not_satisfied< boost::ForwardRangeConcept< const boost::range_detail::filtered_range< main()::<lambda(int)>, int [3] > > >, boost::concepts::constraint< boost::ForwardRangeConcept< const boost::range_detail::filtered_range< main()::<lambda(int)>, int [3] > > >, boost::concepts::requirement< boost::concepts::failed ************ boost::ForwardRangeConcept< const boost::range_detail::filtered_range< main()::<lambda(int)>, int [3] > >::************ > >' /usr/lib/boost/boost/concept/detail/general.hpp:50:8: instantiated from 'boost::concepts::requirement_< void (*)( boost::ForwardRangeConcept< const boost::range_detail::filtered_range< main()::<lambda(int)>, int [3] > > ) >' /usr/lib/boost/boost/range/algorithm/min_element.hpp:43:1: instantiated from 'boost::range_iterator<const T>::ame boost ::range_iterator<const T>::type = boost::filter_iterator< main()::<lambda(int)>, int * > boost::range::min_element( const boost::range_detail::filtered_range< main()::<lambda(int)>, int [3] > & )' test.cpp:8:61: instantiated from here /usr/lib/boost/boost/iterator/filter_iterator.hpp:54:25: error: use of deleted function 'main()::<lambda(int)>::<lambda>()' test.cpp:7:20: error: a lambda closure type has a deleted default constructor

4 8

Timer Callback
by asif saeed 29 May '11

29 May '11

Hi, Can I use Boost Timer or Boost DateTime to trigger callbacks? I just want to be able to have the timer/date-time class trigger my handler functions after every 10 seconds for example or trigger a callback handling function after 25 seconds and die. Is that possible with Boost libraries? I am asking this question because, after a cursory look, it appears to me that there is no such facility right now - if this is true, do you suggest any portable library offering this functionality? Thank you, Asif

3 3

program_options: commands-like style
by Matan Nassau 29 May '11

29 May '11

Hi, How would I implement a program options with a commands style? Something similar to git and other version control systems: ./a.out ls --pattern '[a-z][0-9]+\.txt' --count 7 Here I run a.out with command "ls". The "ls" command has a particular options description. ./a.out read --count Dracula Here I run a.out with command "read". This command also has options of its own, and just to emphasize it I show that the --count option has a different value type here. ./a.out --help Show me general help. ./a.out help ls Does the library support this style? How would I get it to work? Matan

1 0

[exception] Using Boost.Exception infrastructure without using boost::exception
by Mostafa 28 May '11

28 May '11

I'm interested in using the infrastructure in Boost.Exception without using using boost::exception or deriving from it. Is this possible, if so, how? From the documentation, it seems so, but the documentation is not totally clear on this. From what I deduced, one should do: class my_exception {}; //1 throw boost::enable_current_exception(my_exception()); //2 catch(my_exception & ex) { /do stuff .... boost::rethrow_exception(boost::current_exception()); } Though, http://www.boost.org/doc/libs/1_46_1/libs/exception/doc/enable_current_exce… states: Note: Instead of using the throw keyword directly, it is preferable to call boost::throw_exception. This is guaranteed to throw an exception that derives from boost::exception and supports the exception_ptr functionality. And it's not very clear what exactly are the requirements for supporting exception_ptr functionality if one doesn't derive from boost::exception. Thanks, Mostafa

2 11

Python 3.2 (wide-unicode) with Boost 1.46.1 on Ubuntu 10.04 64bit LTS
by Nicholas Yue 28 May '11

28 May '11

Hi, I have a local build of Python 3.2 which have have used to build Python extensions and loaded them successfully in Blender 2.5 (which uses Python 3.2) I am hoping to migrate my bindings to using Boost.Python. I have been been getting error messages from bootstrap.sh and bjam NOTE : I have no problem building boost with Python 2.6.5 which comes with Ubuntu 10.04 LTS e.g. bootstrap.sh ./bootstrap.sh --prefix=/opt/boost/vTrunk-Python-3.2 --without-icu --with-python=/opt/python/v3.2/bin/python3.2 --with-python-version=3.2 >>>>>>>>Building Boost.Jam with toolset gcc... tools/build/v2/engine/src/bin.linuxx86_64/bjam >>>>>>>>Detecting Python root... File "<string>", line 1 >>>>>>>> import sys; print sys.prefix >>>>>>>> ^ >>>>>>>>SyntaxError: invalid syntax e.g. bjam ./bjam --prefix=/opt/boost/vTrunk-Python-3.2 --without-mpi >>>>>>>>gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.3/release/threading-multi/numeric.o >>>>>>>>In file included from ./boost/python/detail/prefix.hpp:13, >>>>>>>> from ./boost/python/numeric.hpp:8, >>>>>>>> from libs/python/src/numeric.cpp:6: >>>>>>>>./boost/python/detail/wrap_python.hpp:50:23: error: pyconfig.h: No such file or directory >>>>>>>>./boost/python/detail/wrap_python.hpp:75:24: error: patchlevel.h: No such file or directory >>>>>>>>./boost/python/detail/wrap_python.hpp:78:2: error: #error Python 2.2 or higher is required for this version of Boost.Python. >>>>>>>>./boost/python/detail/wrap_python.hpp:142:21: error: Python.h: No such file or directory My local build of python is deployed as per the configure script >>>>>>>>/opt/python/v3.2/ >>>>>>>>|-- bin >>>>>>>>|-- include >>>>>>>>| `-- python3.2mu >>>>>>>>|-- lib >>>>>>>>| |-- pkgconfig >>>>>>>>| `-- python3.2 >>>>>>>>`-- share >>>>>>>> `-- man The boost build problem might be directory path naming convention related. If anyone knows the correct to build Boost or Python so they play nice together, please share. Regards

1 1

Boost filesystem library on AIX 5.3
by Manoj Jangid 28 May '11

28 May '11

Hi I am getting following error when I am trying to build filesystem library vacpp.compile.c++ /home/mjangid/boost_rel2/boost/bin.v2/libs/filesystem/build/vacpp/release/threading-multi/v2/src/v2_operations.o "./boost/filesystem/v2/operations.hpp", line 796.73: 1540-1118 (S) The declaration of "end_itr" uses the undefined class "boost::filesystem2::basic_director y_iterator<boost::filesystem2::basic_path<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,boost::filesystem2::path_traits> >" when the class must be complete. "./boost/filesystem/v2/operations.hpp", line 794.21: 1540-0700 (I) The previous message was produced while processing "boost::filesystem2::detail::remove_al l_aux<boost::filesystem2::basic_path<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,boost::filesystem2::path_traits> >(const basic_pat h<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,boost::filesystem2::path_traits> &, file_status)". "./boost/filesystem/v2/operations.hpp", line 497.28: 1540-0700 (I) The previous message was produced while processing "boost::filesystem2::remove_all<boost: :filesystem2::basic_path<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,boost::filesystem2::path_traits> >(const basic_path<std::basic _string<char,std::char_traits<char>,std::allocator<char> >,boost::filesystem2::path_traits> &)". "./boost/filesystem/v2/operations.hpp", line 734.16: 1540-0700 (I) The previous message was produced while processing "boost::filesystem2::remove_all(const path &)". "./boost/filesystem/v2/operations.hpp", line 796.73: 1540-1118 (S) The declaration of "end_itr" uses the undefined class "boost::filesystem2::basic_director y_iterator<boost::filesystem2::basic_path<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >,boost::filesystem2::wpath_traits> >" when the class must be complete. "./boost/filesystem/v2/operations.hpp", line 794.21: 1540-0700 (I) The previous message was produced while processing "boost::filesystem2::detail::remove_al l_aux<boost::filesystem2::basic_path<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >,boost::filesystem2::wpath_traits> >(const basic_path<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >,boost::filesystem2::wpath_traits> &, file_status)". "./boost/filesystem/v2/operations.hpp", line 497.28: 1540-0700 (I) The previous message was produced while processing "boost::filesystem2::remove_all<boost: :filesystem2::basic_path<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >,boost::filesystem2::wpath_traits> >(const basic_path< std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >,boost::filesystem2::wpath_traits> &)". "./boost/filesystem/v2/operations.hpp", line 736.16: 1540-0700 (I) The previous message was produced while processing "boost::filesystem2::remove_all(const wpath &)". xlC_r -c -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_SYSTEM_DYN_LINK=1 -DNDEBUG -qcpluscmt -O3 -qstrict -qfuncsect -qeh -qrtti -I"." -o "/home/mjangid/boost_rel2/boost/bin.v2/libs/filesystem/build/vacpp/release/threading-multi/v2/src/v2_operations.o" "libs/filesystem/v2/src/v2_operations .cpp" ...failed vacpp.compile.c++ /home/mjangid/boost_rel2/boost/bin.v2/libs/filesystem/build/vacpp/release/threading-multi/v2/src/v2_operations.o... ...skipped <p/home/mjangid/boost_rel2/boost/bin.v2/libs/filesystem/build/vacpp/release/threading-multi>libboost_filesystem-mt.so for lack of <p/home/mjangid /boost_rel2/boost/bin.v2/libs/filesystem/build/vacpp/release/threading-multi>v2/src/v2_operations.o... ...skipped <p/home/mjangid/boost_rel2/lib>libboost_filesystem-mt.so for lack of <p/home/mjangid/boost_rel2/boost/bin.v2/libs/filesystem/build/vacpp/release/ threading-multi>libboost_filesystem-mt.so... ...failed updating 1 target... can you please tell me what is wrong or what I am missing? Thanks Manoj Jangid

2 3

Wave - idl parsing
by g w 28 May '11

28 May '11

Hi, I need to parse and generate code for forbade 2.3 idl. Is wave the way to go? Is there a demo our there that shows idl parsing? If yes could you direct me to it pls? Or maybe wave is not the way to go. I'm doing nothing tricky in code generation, logging and operator<< code. Thanks for any info

2 2

[1.47.0] Release schedule
by Beman Dawes 28 May '11

28 May '11

* Monday, June 6: branches/release closed for all changes, except by permission of a release manager. * Monday, June 13: branches/release frozen. Only release managers may commit. Once tests have cycled and the release managers are satisfied with stability, release candidates for the beta will be generated. * Monday, Jun 20: Beta release target date. See June in http://www.boost.org/development/index.html or https://www.google.com/calendar/embed?src=5rorfm42nvmpt77ac0vult9iig@group.… The final release date won't be set until later in the process. Thanks, --Beman

1 0

Boost Unit Testing of DLL's
by Johan Doré 27 May '11

27 May '11

Dear Boost Mailing List We at trying to apply the Boost Unit Testing Framework to our Visual C++ 2010 projects and so far we must conclude that the framework is really excellent and does what we expect. Now most of our modules are developed as DLL's and as we of course want to keep the number of projects and compilation configurations down, we have discussed if we should just distribute the binaries including the test code even though it includes a slight overhead. The thing that is bugging us with that approach is however that the boost_unit_test_framework-vc100-mt-gd-1_46_1.dll seems to be needed for the DLL's to load and we therefore wonder if there is any way around that problem or if you have any other suggestions for us? Best regards Johan Doré, M.Sc. Vice President, CTO Phone : +45 88 20 20 88 Direct : +45 88 20 20 80 Mobile: +45 40 53 93 21 Fax : +45 88 20 20 99 Agern Allé 3 DK-2970 Hørsholm Denmark www.visiopharm.com <http://www.visiopharm.com> This e-mail including attachments is intended for the addressee(s) only and may contain confidential information protected by law. Unauthorised reading, disclosure, copying or distribution of this e-mail or use of information contained herein is strictly prohibited and could violate rights to proprietary information. If you are not an intended recipient, please notify the sender and delete it immediately hereafter. In no event will the sender or Visiopharm be liable for any damages, claims or costs whatsoever or any consequential, indirect incidental damages, any lost profits or lost savings arising from the contents of this mail.

2 1