January 2012 - Boost - lists.preview.boost.org

Latest Boost.Process ?
by Mathias Gaunard 29 Jan '12

29 Jan '12

I wanted to use Boost.Process, and the latest I could fine is from June at <https://github.com/JeffFlinn/boost-process>. Including the main file is enough to get lots of errors, and after fixing them (and there are quite a lot), it appears the functions from the documentation are not there (stdout_to etc.) Is there any recent usable version somewhere?

2 3

[1.49.0] Beta 1 available
by Beman Dawes 28 Jan '12

28 Jan '12

Boost release 1.49.0 beta 1 is now available from SourceForge See http://sourceforge.net/projects/boost/files/ This release contains a new library, Boost.Heap priority queues, and numerous enhancements and bug fixes for existing libraries. For details of what's in the release, see http://beta.boost.org/users/news/version_1_49_0. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

[phoenix] msvc 8.0 errors
by Lorenzo Caminiti 27 Jan '12

27 Jan '12

Hello all, Why doesn't this Phoenix 3.0 code compile? (I'm sure, I'm doing something wrong... but I can't see what...) #include <boost/spirit/include/phoenix.hpp> #define BOOST_TEST_MODULE AddPhoenix #include <boost/test/unit_test.hpp> #include <algorithm> #include <iostream> BOOST_AUTO_TEST_CASE( add_phoenix ) //[add_phoenix { using boost::phoenix::let; using boost::phoenix::local_names::_f; using boost::phoenix::cref; using boost::phoenix::ref; using boost::phoenix::arg_names::_1; int sum = 0, factor = 10; int nums[] = {1, 2, 3}; // Passed to template, `factor` by constant, and defined in expression. std::for_each(nums, nums + 3, let(_f = cref(factor))[ // Unfortunately, body cannot use C++ statement syntax. ref(sum) += _f * _1 // Access `sum` by reference. ]); BOOST_CHECK( sum == 60 ); } //] On MSVC 8.0: ...patience... ...patience... ...found 3219 targets... ...updating 114 targets... compile-c-c++ bin\add_phoenix.test\msvc-8.0\debug\threading-multi\add_phoenix.obj add_phoenix.cpp C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(54) : error C2784: 'boost::phoenix::actor<as_composite<boost::phoenix::multiplies_eval,T0,boost::phoenix::actor<BaseT1>>::type> boost::phoenix::operator *(const T0 &,const boost::phoenix::actor<BaseT1> &)' : could not deduce template argument for 'const boost::phoenix::actor<BaseT1> &' from 'boost::mpl::void_' C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(107) : see declaration of 'boost::phoenix::operator *' C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/mpl/eval_if.hpp(41) : see reference to class template instantiation 'boost::phoenix::result_of_multiplies<X,Y>' being compiled with [ X=const int &, Y=boost::mpl::void_ & ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(76) : see reference to class template instantiation 'boost::mpl::eval_if<C,F1,F2>' being compiled with [ C=boost::mpl::or_<boost::phoenix::is_actor<const int &>,boost::phoenix::is_actor<boost::mpl::void_ &>>, F1=boost::phoenix::re_curry<boost::phoenix::multiplies_eval,const int &,boost::mpl::void_ &>, F2=boost::phoenix::result_of_multiplies<const int &,boost::mpl::void_ &> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/core/detail/composite_eval.hpp(88) : see reference to class template instantiation 'boost::phoenix::multiplies_eval::result<Env,A0,A1>' being compiled with [ Env=boost::phoenix::scoped_environment<boost::phoenix::basic_environment<>,boost::phoenix::basic_environment<>,boost::fusion::vector1<const int &>,boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>>, A0=boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>, A1=boost::phoenix::argument<0> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/core/composite.hpp(60) : see reference to class template instantiation 'boost::phoenix::detail::composite_eval<2>::result<Composite,Env>' being compiled with [ Composite=boost::phoenix::composite<boost::phoenix::multiplies_eval,boost::fusion::vector<boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>,boost::phoenix::argument<0>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>, Env=boost::phoenix::scoped_environment<boost::phoenix::basic_environment<>,boost::phoenix::basic_environment<>,boost::fusion::vector1<const int &>,boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(68) : see reference to class template instantiation 'boost::phoenix::composite<EvalPolicy,EvalTuple>::result<Env>' being compiled with [ EvalPolicy=boost::phoenix::multiplies_eval, EvalTuple=boost::fusion::vector<boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>,boost::phoenix::argument<0>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>, Env=boost::phoenix::scoped_environment<boost::phoenix::basic_environment<>,boost::phoenix::basic_environment<>,boost::fusion::vector1<const int &>,boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/core/detail/composite_eval.hpp(88) : see reference to class template instantiation 'boost::phoenix::plus_assign_eval::result<Env,A0,A1>' being compiled with [ Env=boost::phoenix::scoped_environment<boost::phoenix::basic_environment<>,boost::phoenix::basic_environment<>,boost::fusion::vector1<const int &>,boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>>, A0=boost::phoenix::reference<int>, A1=boost::phoenix::composite<boost::phoenix::multiplies_eval,boost::fusion::vector<boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>,boost::phoenix::argument<0>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/core/composite.hpp(60) : see reference to class template instantiation 'boost::phoenix::detail::composite_eval<2>::result<Composite,Env>' being compiled with [ Composite=boost::phoenix::composite<boost::phoenix::plus_assign_eval,boost::fusion::vector<boost::phoenix::reference<int>,boost::phoenix::composite<boost::phoenix::multiplies_eval,boost::fusion::vector<boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>,boost::phoenix::argument<0>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>, Env=boost::phoenix::scoped_environment<boost::phoenix::basic_environment<>,boost::phoenix::basic_environment<>,boost::fusion::vector1<const int &>,boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/scope/let.hpp(48) : see reference to class template instantiation 'boost::phoenix::composite<EvalPolicy,EvalTuple>::result<Env>' being compiled with [ EvalPolicy=boost::phoenix::plus_assign_eval, EvalTuple=boost::fusion::vector<boost::phoenix::reference<int>,boost::phoenix::composite<boost::phoenix::multiplies_eval,boost::fusion::vector<boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>,boost::phoenix::argument<0>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>, Env=boost::phoenix::scoped_environment<boost::phoenix::basic_environment<>,boost::phoenix::basic_environment<>,boost::fusion::vector1<const int &>,boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/core/actor.hpp(56) : see reference to class template instantiation 'boost::phoenix::let_actor<Base,Vars,Map>::result<Env>' being compiled with [ Base=boost::phoenix::composite<boost::phoenix::plus_assign_eval,boost::fusion::vector<boost::phoenix::reference<int>,boost::phoenix::composite<boost::phoenix::multiplies_eval,boost::fusion::vector<boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>,boost::phoenix::argument<0>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>, Vars=boost::fusion::vector<boost::phoenix::reference<const int>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>, Map=boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>, Env=boost::phoenix::basic_environment<> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/mpl/eval_if.hpp(41) : see reference to class template instantiation 'boost::phoenix::eval_result<Eval,Env>' being compiled with [ Eval=boost::phoenix::let_actor<boost::phoenix::composite<boost::phoenix::plus_assign_eval,boost::fusion::vector<boost::phoenix::reference<int>,boost::phoenix::composite<boost::phoenix::multiplies_eval,boost::fusion::vector<boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>,boost::phoenix::argument<0>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>,boost::fusion::vector<boost::phoenix::reference<const int>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>,boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>>, Env=boost::phoenix::basic_environment<> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/core/actor.hpp(91) : see reference to class template instantiation 'boost::mpl::eval_if<C,F1,F2>' being compiled with [ C=boost::mpl::bool_<false>, F1=boost::mpl::identity<boost::phoenix::detail::error_expecting_arguments>, F2=boost::phoenix::eval_result<boost::phoenix::let_actor<boost::phoenix::composite<boost::phoenix::plus_assign_eval,boost::fusion::vector<boost::phoenix::reference<int>,boost::phoenix::composite<boost::phoenix::multiplies_eval,boost::fusion::vector<boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>,boost::phoenix::argument<0>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>,boost::fusion::vector<boost::phoenix::reference<const int>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>,boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>>,boost::phoenix::basic_environment<>> ] add_phoenix.cpp(29) : see reference to class template instantiation 'boost::phoenix::actor<Eval>' being compiled with [ Eval=boost::phoenix::let_actor<boost::phoenix::composite<boost::phoenix::plus_assign_eval,boost::fusion::vector<boost::phoenix::reference<int>,boost::phoenix::composite<boost::phoenix::multiplies_eval,boost::fusion::vector<boost::phoenix::local_variable<boost::phoenix::local_names::_f_key>,boost::phoenix::argument<0>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>>,boost::fusion::vector<boost::phoenix::reference<const int>,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_,boost::fusion::void_>,boost::phoenix::detail::map_local_index_to_tuple<boost::phoenix::local_names::_f_key,boost::phoenix::detail::unused<1>,boost::phoenix::detail::unused<2>,boost::phoenix::detail::unused<3>,boost::phoenix::detail::unused<4>,boost::phoenix::detail::unused<5>,boost::phoenix::detail::unused<6>,boost::phoenix::detail::unused<7>,boost::phoenix::detail::unused<8>,boost::phoenix::detail::unused<9>>> ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(54) : error C2784: 'boost::phoenix::actor<as_composite<boost::phoenix::multiplies_eval,boost::phoenix::actor<Eval>,T1>::type> boost::phoenix::operator *(const boost::phoenix::actor<Eval> &,const T1 &)' : could not deduce template argument for 'const boost::phoenix::actor<Eval> &' from 'const int' C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(107) : see declaration of 'boost::phoenix::operator *' C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(54) : error C2784: 'boost::phoenix::actor<as_composite<boost::phoenix::multiplies_eval,boost::phoenix::actor<Eval>,boost::phoenix::actor<BaseT1>>::type> boost::phoenix::operator *(const boost::phoenix::actor<Eval> &,const boost::phoenix::actor<BaseT1> &)' : could not deduce template argument for 'const boost::phoenix::actor<Eval> &' from 'const int' C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(107) : see declaration of 'boost::phoenix::operator *' C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(54) : error C2677: binary '*' : no global operator found which takes type 'boost::mpl::void_' (or there is no acceptable conversion) C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(54) : error C2866: 'boost::phoenix::result_of_multiplies<X,Y>::size' : a const static data member of a managed type must be initialized at the point of declaration with [ X=const int &, Y=boost::mpl::void_ & ] C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(54) : error C2057: expected constant expression C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/spirit/home/phoenix/operator/arithmetic.hpp(54) : error C2975: 'N' : invalid template argument for 'boost::mpl::at_c', expected compile-time constant expression C:\Users\lorcam\Desktop\code\boost\trunk.windows\boost/mpl/at.hpp(41) : see declaration of 'N' call "C:\Program Files (x86)\Microsoft Visual Studio 8\VC\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"bin\add_phoenix.test\msvc-8.0\debug\threading-multi\add_phoenix.obj.rsp" ...failed compile-c-c++ bin\add_phoenix.test\msvc-8.0\debug\threading-multi\add_phoenix.obj... ...failed updating 1 target... Thanks a lot! --Lorenzo

1 0

multi_index problems
by brook＠biology.nmsu.edu 26 Jan '12

26 Jan '12

I am trying to use boost.MultiIndex as a class data member and am having difficulty because it seems that calling get<>() will not compile on a NetBSD box (gcc version 4.1.3). The code below illustrates a simple test case. Am I missing something obvious or doing something clearly mistaken? Any help is greatly appreciated. Thanks alot. Cheers, Brook =========================================================================== #include <boost/multi_index_container.hpp> #include <boost/multi_index/sequenced_index.hpp> namespace mi = boost::multi_index; template < typename T > struct container { typedef mi::multi_index_container< T, mi::indexed_by< mi::sequenced< > > > type; }; template < typename T > struct S { typedef typename container< T >::type container_type; void operator () () const { c_.get<0>(); // XXX - will not compile } private: container_type c_; }; int main () { return 0; }

2 1

[codecvt] UTF-8 codecvt
by Artyom Beilis 26 Jan '12

26 Jan '12

Hello, There is an implementation of UTF-8 codecvt facet for various purposes. Unfortunately it has two problems: 1. It does not implement UTF-16 properly (only UCS-2) 2. It requires linking with some library. Boost.Locale provides codecvt facets and I'm planning to add some template for codecvt converter in header files basically Boost.Locale will have header only version of utf-8 codecvt facet and actually very simple pattern to implement any codecvt facet for stateless encoding. I thought about two options: 1. Put it in boost::locale namespace as part of Boost.Locale library 2. Create some small "codecvt" boost library that would provide a simple framework for generation of codecvt facets for boost in general and it would include utf8 codecvt as well. Generally it would look like this: Converter concept: class Converter { public: // copyable Converter(Converter const &); // Max MB length for single Unicode code point int max_length() const; // convert a single mb sequence to code point // returing constants illegal or incomplete in case // if invalid sequence to incomplete sequence uint32_t to_unicode(char const *&begin,char const *end) const; // Convert codepoint u to [begin,end) returning mb length // or returning illegal if it is impossible to convert u to mb sequence // or U is invalid or incomplete if [begin,end) has not enough space uint32_t from_unicode(uint32_t u,char *begin,char const *end) const; }; Note, the converter works only for stateless encodings (which are 99% of all used encodings) And the basic facet would be defined as following: template<typename CharType,typename EncoderType,int size = sizeof(CharType)> class code_converter; Such that for converter concept utf8_converter I can create a utf8_codecvt facet as code_converter<wchar_t,utf8_converter> - is a facet that can be imbued to the locale object. The biggest "trick" is actually implementing codecvt facet to handle UTF-16 properly and it is implemented in Boost.Locale. So Boosters: Do You Want It Boost.Codecvt or it is fine to have it as part of Boost.Locale. In either case it would be header only "codecvt" framework. Artyom Beilis -------------- CppCMS - C++ Web Framework: http://cppcms.sf.net/ CppDB - C++ SQL Connectivity: http://cppcms.sf.net/sql/cppdb/

2 2

Scoped Enum Emulation
by Joshua Boyce 26 Jan '12

26 Jan '12

I'm currently updating some of my code to take advantage of C++0x features where available, but I also want to retain backwards compatibility with C++03. I was looking at scoped enums and noticed a thread on the mailing list by Beman Dawes discussing a scoped enum emulation implementation for Boost. I see that it's currently being used by Boost, and resides in /boost/detail/scoped_enum_emulation.hpp. My question is, why is this an implementation detail? Would it be possible for it to be moved to Boost.Config with the other 'helper' macros like BOOST_CONSTEXPR? Obviously it's not hard to reimplement, but I figured that it would be useful to other library users, so it would be best (imo) if it were moved somewhere public, rather than being hidden away. Thanks.

4 10

Re: [boost] [lexical_cast] Fast conversion from boost::iterator_range<std::string::iterator>?
by Matthew Chambers 26 Jan '12

26 Jan '12

On Oct 13, 2011 Michel Morin wrote: > lexical_cast made optimizations for some types (such as `std::string`) > to achieve better performance. But, from my experience, > it seems that lexical_cast does not make any optimization for > `boost::iterator_range<std::string::iterator>`. > > Is there any plan to add optimization for such iterator ranges? > Currently, > - `lexical_cast<int>(std::string(iter_rng.begin(), iter_rng.end()))` > is faster > than `lexical_cast<int>(iter_rng)`. > - Assuming it is safe to use `std::atoi`, > `std::atoi(&iter_rng.front())` is faster > than both of the above two methods. > (`iter_rng` is an instance of `boost::iterator_range<std::string::iterator>`.) > > Regards, > Michel This post was on the boost users list but never got a reply. I figure it might be a better fit on the developer list. I too would like to see optimized conversions work on string ranges; what's the point in doing a fast conversion if you have to do a string copy first? :) -Matt

8 16

Attribute names with underscores for GCC
by Michel Morin 26 Jan '12

26 Jan '12

Recently, Petr Machata created several trac tickets for requesting the use of attribute names with underscores for GCC. Since there is no link to the GCC's documentation in the tickets, I'd like to put a link to the documentation. In the GCC's manuals --> "Extensions to the C Language Family" --> "Declaring Attributes of Functions", "Specifying Attributes of Variables", and "Specifying Attributes of Types", there is description about attributes with preceding and following `__`: You may also specify attributes with `__' preceding and following each keyword. This allows you to use them in header files without being concerned about a possible macro of the same name. For example, you may use __noreturn__ instead of noreturn. Here are links to the gcc-2.9.5's documentation: http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC84 http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC90 http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC91 I also checked manuals of gcc-3.0.4 and 4.0.4, and found the same description. Hope this helps, Michel

2 2

[assert] [exception] Fast output binary file size growth
by Antony Polukhin 26 Jan '12

26 Jan '12

Greetings, When BOOST_ENABLE_ASSERT_HANDLER is defined or BOOST_THROW_EXCEPTION used, compiler generates a string with function name. If a function is templated, compiler will generate a string for each function template. That leads to a huge binary files. Consider the following example: #define BOOST_ENABLE_ASSERT_HANDLER #include <boost/assert.hpp> template <class MplVectorT> void do_something(bool v) { BOOST_ASSERT(v); } void do_something<boost::mpl::vector<int, double>>(v); void do_something<boost::mpl::vector<int, int>>(v); This two functions will generate strings like "void do_something<MplVectorT>(bool v) [with MplVectorT = boost::mpl::vector<int, double> ]" and "void do_something<MplVectorT>(bool v) [with MplVectorT = boost::mpl::vector<int, int> ]". When there is more mataprogramming, one such string can have a size of a few kilobytes. In one of my binaries, such strings take more than 50 megabytes of binary size (total size of binary is 70 megabytes). I`ve got a patch and documentation update for Boost.Assert and Boost.Exception, that allow to disable construction of such strings or to use different macro for current function name (for example macro that prints ONLY function name). Is there interest in this feature/patches? Best regards, Antony Polukhin

2 2

[filesystem] noexcept question? [was: Scoped Enum Emulation]
by Beman Dawes 26 Jan '12

26 Jan '12

On Tue, Jan 24, 2012 at 8:38 PM, Joshua Boyce <raptorfactor(a)raptorfactor.com> wrote: > While I've got your attention, I have a similar question along the same > lines. I notice in the mailing list archives that you added some noexcept > related macros to Boost.Config on trunk back in October 2011, I can't see > them in the current trunk or release though. What happened to those? They won't go in 1.49.0, but will begin to go into trunk within the next month. Likewise some other C++11 support, such as rvalue reference signatures. --Beman

2 1

[filesystem] documentation typo
by Greg Rubino 26 Jan '12

26 Jan '12

Hello, It looks like there's some copy/paste residue in http://www.boost.org/doc/libs/1_48_0/libs/filesystem/v3/doc/reference.html#… basic_filesystem_error has become filesystem_error, but in the anchor it's still called 'basic_filesystem_error', and also there are a couple of references on the page to basic_filesystem_error. This momentarily confused me when I was moving a codebase from v1 to v3 yesterday, so I thought it was worth mentioning. I've entered a trac ticket for this issue: https://svn.boost.org/trac/boost/ticket/6448 but I would be delighted to submit a patch for this since I've been wanting to get more involved in Boost, but it would be my first time doing and I'm not quite sure how to go about it. I assume that it involves checking out the trunk and modifying the necessary files, but I'm not sure after that. Greg

2 1

Boost.Application
by Renato Tegon Forti 26 Jan '12

26 Jan '12

Hi All, I have the first prototype of the "Boost.Application" ready! I would like to receive comments so I can refine the library. Please send your feedback to re.tf(a)acm.org 0) Introduction A Boost.Application allows a developer run your application as a Windows service, as a Unix/Linux daemon, or as a usual interactive application (terminal) without the need to add extra code, the library abstract OS specific API and provide a ease common interface. In case of server application, developer need only compile your code on a Windows to have a ready to play Windows Service or in a UNIX/Linux to have Daemon. CTRL-C signals and SCM (Service Control Manager) controls handlers are available for terminating, pause/resume(windows) the application constructively and many other until methods are available in application class like a single instance running limitation! 1) Download: https://sourceforge.net/projects/boostapp/ 2) Installation: The library is one: Automatic linking You should unpack the files and copy: Boost.Application_pre_alpha_1\boost\application To: boost_1_48_0\boost and, Boost.Application_pre_alpha_1\libs\application To: boost_1_48_0\libs 3) Build Then you must build, for example (in windows): bjam toolset=msvc-9.0 variant=debug threading=multi link=shared define=_BIND_TO_CURRENT_VCLIBS_VERSION 4) Documentation The project has an incomplete documentation: Boost.Application_pre_alpha_1\libs\application\doc\html\index.html 5) Use however, the tutorial explains how to use the lib, and that generally goes like this: ---------------------------------------------------------------------------- -------------------- #include <boost/application/engine.hpp> class myapp : public boost::application::application { protected: int main(const std::vector<std::string>& args) { // your application logic here! while(1) { std::cout << "Hello Boost.Application!" << std::endl; // ... if(state() == boost::application::application_stoped) { break; } } return 0; } }; BOOST_APP(myapp, "MainTutorial1", "Boost.Application Main Tutorial 1!", boost::application::default_application_type, 1, 0, 1) ---------------------------------------------------------------------------- -------------------- The folder: Boost.Application_pre_alpha_1\libs\application\example\tutorial Has all tutorial files! I tested the lib on Windows VC9 (Windows Service) and Ubuntu 11 GCC 4 (Daemon)! 6) Questions: * Is there any interest in this library? * If Yes! What are the refinements? (see todo, for some) Please send your feedback to re.tf(a)acm.org Thanks to all Renato

3 5

Boost.Application (PART II)
by Renato Tegon Forti 26 Jan '12

26 Jan '12

Hi all, I want to emphasize: 1) This is a prototype, a starting point to find out if this is an interesting lib to boost! 2) And if 1 is true! I will compile all comments and make modifications to meet "boost"! My doubt is if this lib don't violate: "The library must be generally useful and not restricted to a narrow problem domain." About comments of friends! First, thank you for the comments! They always show a new way of doing things, which I had not thought of! This is the main reason I'm doing (trying to) this lib, to have the opportunity to learn (and contribute) with you! I will try to enumerate the comments, and then build a path to follow for next version (if [1] is satisfied. Do you think I need more votes to continue the effort?) a) >>So selling it as "ready to play" UNIX/Linux daemon is a bit - erm - exaggerating. Sorry about this, I will change this description! I agree with you! Sorry! b) >> Why is the application not a functor or even a function? . Again I agree with you! This is a better way!, for sample I can handle exception in my main too! Thanks about this suggestion! >> I don't like it, though I don't have an alternative solution at hand. Somehow this feels very clumsy with that init() method. As example of a pure OO approach you could have a look at Qts QApplication. I will look QApplication! If you have time! You could describe what you think would be the right path follows in more detail, I appreciate it! c) >> The biggest concern for me is that you're using narrow strings I will provide wide strings. I don't know how yet. I will check Boost.Filesystem! Besides, there is other example to follow? For sample, I need use W version (GetModuleFileNameW) on all? And use a function like this to convert: inline void convert(const char* from, std::wstring & to, const codecvt_type& cvt) D) Other question, to handle exceptions! Any Idea? e) "Install and uninstall windows service" functionality, be a part of the application instead of a separate one and using a callback. f) * In the unknown mode, the program can run in either mode provided someone puts something in the command line. Could that rather be a callback maybe post initialize such that we tell your application which one we want. This way the developer controls his command line. After all, it might not come from the command line but instead from a configuration file. -------------------------------------------------------------------------- What else? Thanks for help!!!

1 0

boost filesystem path as utf-8?
by Emil Dotchevski 25 Jan '12

25 Jan '12

Hello, I understand that the path class .native() member function's return type differs depending on the platform (wstring on windows, for example.) Is there a way to get the path as a utf-8 string regardless of the platform? Likewise, is there a way to construct a path object from a utf-8 string regardless of the platform? Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

4 9

[log][phoenix] Questions on porting to phoenix
by Andrey Semashev 25 Jan '12

25 Jan '12

Hi, [My apologies for the long post] I'm trying to port filters and formatters of Boost.Log to Boost.Phoenix and I'm not sure I understand what's the best way to go. Hope someone can help me out. A short introduction of the terms and what is currently available. * An attribute value is a type-erased value, something similar to boost::any but with more advanced interface to allow visitation and extraction of the stored value. * A log record is an object which contains a set of named attribute values. For simplicity, let's say: class attribute_value; typedef map< string, attribute_value > attribute_values_view; class record { public: attribute_values_view const& attribute_values() const; string const& message() const; }; * A filter is a function that accepts attribute values and returns a bool: typedef function< bool (attribute_values_view const&) > filter; The filter is assumed to pass the log record if it returns true. * A formatter is a function that accepts a log record and a stream and outputs strings or attribute values to the stream: typedef function< void (ostream&, record const&) > formatter; * I already have the code that extracts attribute values from log records. What I'm trying to achieve is something along these lines (this is not a finalized interface yet): enum my_severity { info, warning, error }; BOOST_LOG_REGISTER_ATTRIBUTE("Severity", severity, my_severity) filter flt = severity >= warning; formatter fmt = stream << "[" << severity << "] " << message; Here, "stream" and "message" are keywords provided by Boost.Log, the former is a placeholder for the stream argument of the formatter function, and the latter returns the result of the record::message() method. Now, the BOOST_LOG_REGISTER_ATTRIBUTE macro is what I'm struggling on. It should create a new keyword (severity) which should: 1. Be a POD object to be statically initialized. 2. Contain the information on the type (my_severity) and name ("Severity") of the attribute to be able to extract it from the log record. 3. Be a Phoenix object to initiate lazy expression generation. >From what I gathered from the docs and examples, the generated keyword should be a terminal, in terms of Proto. Am I correct? In order to produce the value, during the evaluation the keyword should receive either a log record or a attribute_values_view and I can't quite understand how do I do that. Basically, I don't quite understand how do I declare and implement a terminal so that it works with Phoenix. This question also applies to the "stream" and "message" keywords but I suspect the solution will be similar. Maybe there is an example of doing this in the docs or elsewhere. I'll be glad if someone provides a link or example of doing this. Thanks in advance.

5 11

[quickboost] single HTML page?
by lcaminiti 24 Jan '12

24 Jan '12

Hello all, Is there a way to have quickbook generate a single HTML page? (Maybe some XSL param...) Right now, different sections appear on different HTML pages. But for a very simple doc, I only have 3 short sections and it'd make more sense for them to be displayed on a single page while still remain separate section and appear separately in the table of context. Thanks a lot. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-quickboost-single-HTML-page-tp4323… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 1

Bug reports - Showstoppers and Regressions
by Marshall Clow 24 Jan '12

24 Jan '12

There are a couple of useful reports on svn.boost.org: Active Showstoppers: https://svn.boost.org/trac/boost/report/43 Active Regressions: https://svn.boost.org/trac/boost/report/30 To shortcut part of the discussion, here are some definitions (taken from https://svn.boost.org/trac/boost/wiki/TicketWorkflow) • Showstopper - this problem is so bad, that we should hold up a release if it's not fixed. Note that the release managers and/or the library maintainers may have different opinions. • Regression - something used to work (in a previous release), but no longer does. IMHO, these bugs should be at least looked at before each release. -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

8 15

[BGL] Any interest in updated maximum adjacency search?
by Fernando Vilas 23 Jan '12

23 Jan '12

Hi, As a part of my graduate research, I have been using the maximum adjacency search algorithm. In the BGL, it is implemented in the stoer_wagner_min_cut functions. I have already broken it out of there, to be a search with a visitor, like BFS. I also implemented a dummy visitor and wrote visitors for my research. It would be very easy to implement a min-cut visitor so that the Stoer-Wagner functionality is maintained without a public API change. As a contributor in other FLOSS projects, I would like to contribute this code back to the Boost library, under the Boost license, if there is interest in the code. That said, this will be my first contribution to Boost, so I would most likely need someone willing to help me navigate the approval process and let me know where the code needs to be improved to meet the normally high standards on this project. -- Thanks, Fernando Vilas fvilas(a)iname.com

2 2

[quickbook] email tag?
by lcaminiti 21 Jan '12

21 Jan '12

Hello all, Is there a preferred way or special tag to specify the author's email within the [library ...] tag? [library Boost.LocalFunction [author [Caminiti, Lorenzo]] ... ] Thanks. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-quickbook-email-tag-tp4310264p4310… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 4

[local] name (was Re: "protected" APIs)
by Lorenzo Caminiti 21 Jan '12

21 Jan '12

On Mon, Jan 16, 2012 at 6:06 AM, Thomas Klimpel <Thomas.Klimpel(a)synopsys.com> wrote: > Hartmut Kaiser wrote: >> > On 01/02/2012 10:25 AM, Lorenzo Caminiti wrote: >> > > Hello all, >> > > >> > > Boost.Closure (formerly, Boost.Local) needs to use some macros, >> types, >> > > etc that are currently marked private in Boost.ScopeExit: >> > >> > Boost.Closure? I really don't like that name is at implies functional >> > programming capabilities. Didn't you decide to name it >> Boost.LocalFunction >> > instead? >> >> I second that concern. I wouldn't like for the local function library >> to >> claim the name 'closure'. >> This would be >> >> a) totally misleading and >> b) inhibits to give that name to a potential real closure library in >> the >> future. > > +1 As I said before, I'm equally happy with Boost.LocalFunction and Boost.Closure. I'm checking with my review manager about going back from Closure to LocalFunction given that a few people have now expressed such a preference. I'll keep everyone posted :) > Or more precisely, just ignoring mails questioning the name Boost.Closure is not good style. In a functional programming language, many things can be done with a closure (for example returning it from a function), and it is unclear to me, whether Boost.Local really is able to approximate this functionality in a sufficiently usable way. It might be true, but then please point me to the corresponding passage in the documentation. Boost.Local docs do not (yet) explain how and when local functions can be returned because that was a homework from the review. I'm pasting below a few examples that I will include in the docs: //[test_return_inc_cpp #include <boost/closure.hpp> #include <boost/function.hpp> #define BOOST_TEST_MODULE ReturnInc #include <boost/test/unit_test.hpp> boost::function<int (void)> inc(int& value) { int BOOST_CLOSURE(bind& value) { return ++value; } BOOST_CLOSURE_END(i) return i; } BOOST_AUTO_TEST_CASE( return_inc ) { int value1 = 0; // Reference valid in scope where closure is used. boost::function<int (void)> inc1 = inc(value1); int value2 = 0; boost::function<int (void)> inc2 = inc(value2); BOOST_CHECK( inc1() == 1 ); BOOST_CHECK( inc1() == 2 ); BOOST_CHECK( inc2() == 1 ); BOOST_CHECK( inc1() == 3 ); } //] //[test_return_setget_cpp #include <boost/closure.hpp> #include <boost/function.hpp> #define BOOST_TEST_MODULE ReturnSetGet #include <boost/test/unit_test.hpp> #include <string> boost::function<void (std::string const&)> set; boost::function<std::string const& (void)> get; void action(void) { // State `message` hidden behind access functions from here. BOOST_CHECK( get() == "abc" ); set("xyz"); BOOST_CHECK( get() == "xyz" ); } BOOST_AUTO_TEST_CASE( return_setget ) { std::string message = "abc"; // Reference valid where closure used. void BOOST_CLOSURE(bind& message, std::string const& text) { message = text; } BOOST_CLOSURE_END(s) set = s; std::string const& BOOST_CLOSURE(const bind& message) { return message; } BOOST_CLOSURE_END(g) get = g; action(); } //] //[test_return_derivative_cpp #include <boost/closure.hpp> #include <boost/function.hpp> #define BOOST_TEST_MODULE ReturnDerivative #include <boost/test/unit_test.hpp> boost::function<int (int)> derivative(boost::function<int (int)>& f, int dx) { int BOOST_CLOSURE(bind& f, const bind dx, int x) { return (f(x + dx) - f(x)) / dx; } BOOST_CLOSURE_END(deriv) return deriv; } BOOST_AUTO_TEST_CASE( return_derivative ) { int BOOST_CLOSURE(int x) { return x + 4; } BOOST_CLOSURE_END(add2) boost::function<int (int)> a2 = add2; // Reference valid where closure used. boost::function<int (int)> d2 = derivative(a2, 2); BOOST_CHECK( d2(6) == 1 ); } //] //[test_return_this_cpp #include <boost/closure.hpp> #include <boost/function.hpp> #define BOOST_TEST_MODULE ReturnThis #include <boost/test/unit_test.hpp> struct number { number(int value) : value_(value) {} boost::function<int (void)> inc(void) { int BOOST_CLOSURE(bind this_) { return ++this_->value_; } BOOST_CLOSURE_END(i) return i; } private: int value_; }; BOOST_AUTO_TEST_CASE( return_this ) { number n1 = 0; // Object valid in scope where closure is used. boost::function<int (void)> inc1 = n1.inc(); number n2 = 0; boost::function<int (void)> inc2 = n2.inc(); BOOST_CHECK( inc1() == 1 ); BOOST_CHECK( inc1() == 2 ); BOOST_CHECK( inc2() == 1 ); BOOST_CHECK( inc1() == 3 ); } //] Thanks. --Lorenzo

3 2

[quickbook] changing paths
by lcaminiti 21 Jan '12

21 Jan '12

Hello all, How can I change the paths were Boost.QuickBook looks for the following files? 1) CSS and icon images by default from BOOST_ROOT/doc. 2) Navigation bar by default from BOOST_ROOT/tools/boostbook/xls. Essentially, I'd like to put the CSS, icon images, and navbar into a different path. Also, I'd like to change the navbar to one of my own. Thanks a lot. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-quickbook-changing-paths-tp3925967… Sent from the Boost - Dev mailing list archive at Nabble.com.

4 4

[review] WANTED: Review Managers
by Ronald Garcia 20 Jan '12

20 Jan '12

Hi all, Currently the Boost review schedule has 8 libraries ready for review, but we need some individuals to volunteer to be review managers so that we can schedule reviews for them. In general review managers are active boost participants, including library contributors, infrastructure contributors, and other mailing list participants with a substantial track record of constructive participation. The libraries on the review schedule are as follows (the "(M)" simply means that a manager is needed): * Join (M) * Pimpl (M) * Sorting (M) * Quaternions, Vectors, Matrices (M) * Variadic Macro Data (M) * Block Pointer (M) * Singularity (M) * Predef (M) If you are interested, able, and qualified to be a review manager for one of these libraries, please contact myself and/or John Phillips. Thank you. Best, Ron

1 0

[move] error: duplicate 'inline'
by Vicente J. Botet Escriba 19 Jan '12

19 Jan '12

Le 16/01/12 20:48, Beman Dawes a écrit : > On Mon, Jan 16, 2012 at 1:38 PM, Vicente J. Botet Escriba > <vicente.botet(a)wanadoo.fr> wrote: >> Le 16/01/12 19:30, Vicente J. Botet Escriba a écrit : >> >> Hi there is a minor Bug on trunk regression test for Boost.Move and all the >> libraries using it. >> >> Test output: Sandia-darwin-4.4_0x - move - back_move_inserter / >> darwin-4.4_0x >> Rev 76539 / Mon, 16 Jan 2012 11:49:32 +0000 >> Report Time: Mon, 16 Jan 2012 16:05:03 +0000 >> Compile [2012-01-16 12:32:57 UTC]: fail >> >> "/opt/local/bin/g++-mp-4.4" -ftemplate-depth-128 -std=gnu++0x -O0 >> -fno-inline -Wall -g -gdwarf-2 -fexceptions -DBOOST_ALL_NO_LIB=1 -I".." -c >> -o >> "/Volumes/scratch/kbelco/boost/results/boost/bin.v2/libs/move/test/back_move_inserter.test/darwin-4.4_0x/debug/link-static/back_move_inserter.o" >> "../libs/move/test/back_move_inserter.cpp" >> >> In file included from ../libs/move/test/back_move_inserter.cpp:11: >> ../boost/move/move.hpp:486: error: duplicate 'inline' >> ../boost/move/move.hpp:522: error: duplicate 'inline' >> >> >> Could this be fixed quickly? >> >> >> It seems that the problem has been merged to the release branch also. > Shouldn't this be posted on the main list? Maintainers don't > necessarily read the testing list. > > > Ion, could you analyze this blocking issue? Vicente

4 3

Permission to merge to release a remove-warnings-update
by Barend Gehrels 19 Jan '12

19 Jan '12

Hi, Christophe sent me this week a patch to avoid many warnings about unused parameters in many files. I applied that (all but one file which was not about unused parameters) and fixed some more. So this is a low-risk update which might be convenient for many users. All tests run fine. Do I have permission to still merge this with the Release branch? Thanks, Barend

1 0

Vote Boost Up for SourceForge Project of the Month
by Dave Abrahams 19 Jan '12

19 Jan '12

Folks, I was just informed that Boost is a top contender for SourceForge's February Project Of The Month. The vote is happening on TwtPoll, here: http://twtpoll.com/7vt4lq It's pretty close, so if you could vote Boost up, it could be good for our profile and our future. Thanks! -- Dave Abrahams BoostPro Computing http://www.boostpro.com

9 8