December 2011 - Boost - lists.preview.boost.org

Re: [boost] Proposal for a Differential Evolution C++ library
by Adrian Michel 12 Dec '11

12 Dec '11

Hi Oliver, On 12/11/2011 9:52 PM, Oliver Kullmann wrote: > > >> I took a peak at the overview and some of the other pages and from >> what I can see initially, it looks like a very useful library for >> artificial intelligence. I have very limited knowledge in the field >> but this is something that grabs my interest, so if it's made public >> I'll definitely use it for future projects that would benefit from >> it. Of course whether it is suitable for Boost is for others to >> determine. >> >> Philip Bennefall >> > > It seems to me that the application domain is not "artificial intelligence", > but arbitrary optimisation problems. > In general, I would like to see more algorithms in Boost. > This library seems a good example, judging from its applicability: > it seems to be widely applicable. > > Oliver > Yes, you are correct, DE is generic, doesn't know or care what the nature of the objective function is. Thanks, Adrian

1 0

Re: [boost] Boost.Thread and Boost.Move collision
by onlyone＠senet.com.au 11 Dec '11

11 Dec '11

>Vicente J. Botet Escriba: >> Le 01/12/11 18:11, onlyone(a)senet.com.au a ?crit : >>>>> 1) Move Boost.Move elements to boost::move:: namespace >>>>> 2) Move Boost.Thread elements to boost::thread namespace >>>>> 3) Modify Boost.Thread to make use of Boost.Move >>>>> >>>> FWIW, I think 3) is what sounds obvious to me. Now maybe there's >>>> reasons to >>>> avoid coupling those libraries together but I'm not sure what they >>>> would be. >>>> >>>> Philippe >>> Hi, >>> I have been working on a patch to do just that. I have not run into >>> any major issues so far. Modifying Boost.Thread to use >>> Boost.Move solves two problems: >>> >>> 1) It fixes the name collision (obviously). >>> 2) It allows types that have been designed to use the Boost.Move >>> emulation to interoperate with Boost.Thread. (This is relevant >>> for futures/promises.) >>> >> Could you post the patch or attach it to a Trac ticket? >> >Any news of this patch? > I have been working on it. I was able to implement the basic functionality in a matter of hours (Boost.Move is very easy to use). Unfortunately, I have been having trouble "Boostifying" the code, as I am unfamiliar with the reasons for many of the workarounds in the existing code (I am worried about causing regressions in these). I have not yet started on the documentation or tests. This patch is still my #1 priority, so expect it soon! Regards, Evan Wallace

2 1

update from 1_44 to 1_48: build questions
by Oliver Kullmann 11 Dec '11

11 Dec '11

Hello, we want to update from 1_44_0 to 1_48_0. Our old build-process is as follows (for Linux): 1. cd tools/jam/src 2. CC="$(gcc_call)" CFLAGS="-fno-strict-aliasing" ./build.sh cc 3. cp bin.*/bjam $(boost_base_build_dir) 4. cd ../../.. 5. echo "using gcc : $(gcc_version) : $(gcc_call) : ;" > $(boost_base_build_dir)/bjam_config 6. $(boost_base_build_dir)/bjam --user-config=$(boost_base_build_dir)/bjam_config --prefix=$(boost_installation_dir) --build-dir=$(boost_build_dir) install --without-python --without-wave --without-mpi -sBZIP2_INCLUDE=$(bzip2_source_library) -sBZIP2_LIBPATH=$(bzip2_link_library) It seems that "b2" is (just) bjam? However it is not really clear from the documentation how to build (and use) bjam (apparently via boostrap?)? And then apparently some of the above parameters of bjam, for example prefix, are now parameters of bootstrap? We would be glad if somebody could tell us (or some link) how to update the above process. Thanks in any case for your consideration. Oliver

2 2

[chrono] i/o to locale or not to locale
by Vicente J. Botet Escriba 10 Dec '11

10 Dec '11

Hi all, currently Chrono provides a limited localization interface for duration and time_point I/O that is not satisfactory. The current implementation Boost.Chrono V1.2 (Boost 1.48) is based on the alternative A1 (see below) in which the hour,minute,second and the epoch can be localized. This could give the impression that chrono i/o is localized, but as Aryton as signaled it is not enough. I'm working on redesigning the chrono i/o in order to make a proposal with Howard Hinnant to the C++ committee. Two main alternatives A1- follow the formatting of recognized international body as ISO. A2- Add localization of specific units and epoch to the preceding format. It seems that the localized alternative seems to have less chances to be adopted, as no other library in the standard is providing these kind of facilities, and locale message facility is not completely satisfying. Things could change if we had a concrete proposal for improving the standard locale library (in which Aryton seems to be working IUC). More detail on the two alternatives: A1- Provide formatted i/o following the ISO 80000 http://en.wikipedia.org/wiki/ISO/IEC_80000, http://en.wikipedia.org/wiki/ISO_31-1, The format for duration could be <value> <unit> With unit been day, hour, minute, second, decisecond, centisecond, ..., decasecond, hectosecond, ... Note that the unit is always in singular form and in English. Next follows several valid inputs for duration 3 day 9 hour 1 second 0 second -1 second 3.77 millisecond 34 [1/30]second time_points could be formatted as <duration> <since epoch> where <since epoch> is a string that identifies the starting point of the epoch's clock, e.g. since boot, since process startup, .... The string associated to each clock are fixed and configurable specializing the trait clock_string Next follows several valid inputs for time_point. 123456 second since boot A1.a We can also consider ISO 8601. IMO, an acceptable format for durations could be a variation of the extended format independently of the date. <hours>:<minutes>:<seconds>[.fractional_seconds] Note that <hours> here is not limited to 24, and gives the total number of hours. A1.b An additional alternative could be to represent a duration as following a variant of the period representation: P[n]Y[n]M[n]DT[n]H[n]M[n]S in which the year and month are represented by days. E.g. P[n]DT[n]H[n]M[n]S[n]F P1234DT12H30M5S555F A2 - Make durations and time point i/o locale dependent. Based on the previous alternative, add the possibility to add specific locale facets that could format a duration following the pattern <value> <unit> <unit> <value> <hours><:><minutes><:><seconds>[<.>fractional_seconds] Here <value> and <unit> will be formatted following the specific locale and in this case the unit could have specific plural forms. For example in French the user could specialize the facets so that she could get 1 jour 3 jours 9 heures 1 seconde 0 secondes -1 seconde 3.77 milliseconds 34 [1/30] de seconde and in Spanish 1 segundo 0 segundo -1 segundo Add the possibility to add specific locale facets that could format a time_point following the pattern <duration> <epoch> <epoch> <duration> system_clock::time_point is a special case that should be formatted as a localized date, relative to the epoch 1900/01/01. A3 - Add on top of A2 some _byname facets. The fist alternative is in line with the money standard locale category that uses standard symbols, as $ or USD. It has the drawback that the <value> could be localized while the <unit> is not, e.g. 1,234 second Note the use of ','. The third alternative is IMO closer to the user expectations, but needs a better locale messages/by_name facet. The second alternative is a pragmatic one that left the possibility to build A3 when a satisfying messages/by_name facet is available. Boost.Chrono 2.0 in the trunk is a prototype of A2, that doesn't provides facets by locale name, only a default English implementation. That means that for the time been, the user needs to imbue a locale with her specific facet to get the expected localization (See french.cpp example in the SVN repository) What the Boost community think about this? Towards which alternative should Boost.Chrono move? Should Boost.Chrono wait until a concrete standard proposal is accepted? Thanks in advance, Vicente

2 6

Re: [boost] Boost.Thread and Boost.Move collision
by onlyone＠senet.com.au 10 Dec '11

10 Dec '11

>> >> 1) Move Boost.Move elements to boost::move:: namespace >> 2) Move Boost.Thread elements to boost::thread namespace >> 3) Modify Boost.Thread to make use of Boost.Move >> > >FWIW, I think 3) is what sounds obvious to me. Now maybe there's reasons to >avoid coupling those libraries together but I'm not sure what they would be. > >Philippe Hi, I have been working on a patch to do just that. I have not run into any major issues so far. Modifying Boost.Thread to use Boost.Move solves two problems: 1) It fixes the name collision (obviously). 2) It allows types that have been designed to use the Boost.Move emulation to interoperate with Boost.Thread. (This is relevant for futures/promises.) Evan Wallace

2 2

Phoenix Quoting
by paul Fultz 09 Dec '11

09 Dec '11

Hi, Is there a way using Phoenix to do quoting? I would like to do something like this: quote x("x"); string s = (x < 3 and x > 0)(); //s = "x < 3 and x > 0" Is there some kind of quote class in Phoenix or a way to create a quote class? Thanks, Paul

3 5

[boost-dev] compilation warnings questions by a newbee
by Rai, Neeraj 09 Dec '11

09 Dec '11

Hi, I am writing my first boost program and having trouble with the compiler warning against boost 1.44.0. Is there any way to get rid of those warnings so I can focus on real warnings in my code ? This seems to happen with newer version of g++ : tried 4.4.5 and 4.6 The gist of warning is : boost_1_44_0/include/boost/mpl/aux_/integral_wrapper.hpp:73:96: warning: the result of the conversion is unspecified because '-0x00000000000000001' is outside the range of type 'boost::numeric::udt_builtin_mixture_enum' [-Wconversion] Any help or pointers are appreciated. Neeraj ====== The following program is a cut down version of my code, just declares sregex #include <iostream> #include <boost/xpressive/xpressive.hpp> int main (int _argc, const char** _argv) { std::cout << "argc=" << _argc << " argv=" << _argv << std::endl; using namespace boost::xpressive; std::string keyword(""); sregex const re(sregex::compile(keyword, sregex::icase)); } ====== The following cmd is used to build it (tried g++ v 4.4.5 and 4.6 with same results) g++ -ftemplate-depth-128 -O0 -fno-inline -Wall -g -Wconversion -Wno-strict-aliasing -Wextra -Wnon-virtual-dtor -Wno-missing-field-initializers -Wno-array-bounds -Wno-ignored-qualifiers -Wno-parentheses -Wno-strict-aliasing -fPIC -DBOOST_ALL_NO_LIB -I/work/loc1/atddds -I/work/loc1/boost_1_44_0/include -Iinclude -c -o boost_regex_test.o boost_regex_test.cpp ====== The following cmd is used to build it (tried g++ v 4.4.5 and 4.6) g++ -ftemplate-depth-128 -O0 -fno-inline -Wall -g -Wconversion -Wno-strict-aliasing -Wextra -Wnon-virtual-dtor -Wno-missing-field-initializers -Wno-array-bounds -Wno-ignored-qualifiers -Wno-parentheses -Wno-strict-aliasing -fPIC -DBOOST_ALL_NO_LIB -I/work/loc1/atddds -I/work/loc1/boost_1_44_0/include -Iinclude -c -o boost_regex_test.o boost_regex_test.cpp In file included from /work/loc1/boost_1_44_0/include/boost/mpl/integral_c.hpp:32:0, from /work/loc1/boost_1_44_0/include/boost/type_traits/integral_constant.hpp:11, from /work/loc1/boost_1_44_0/include/boost/type_traits/detail/bool_trait_def.hpp:15, from /work/loc1/boost_1_44_0/include/boost/type_traits/is_volatile.hpp:40, from /work/loc1/boost_1_44_0/include/boost/type_traits/remove_const.hpp:14, from /work/loc1/boost_1_44_0/include/boost/proto/proto_fwd.hpp:25, from /work/loc1/boost_1_44_0/include/boost/xpressive/xpressive_fwd.hpp:53, from /work/loc1/boost_1_44_0/include/boost/xpressive/detail/detail_fwd.hpp:24, from /work/loc1/boost_1_44_0/include/boost/xpressive/regex_primitives.hpp:21, from /work/loc1/boost_1_44_0/include/boost/xpressive/xpressive_static.hpp:24, from /work/loc1/boost_1_44_0/include/boost/xpressive/xpressive.hpp:18, from boost_regex_test.cpp:2: /work/loc1/boost_1_44_0/include/boost/mpl/aux_/integral_wrapper.hpp: In instantiation of 'mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>': /work/loc1/boost_1_44_0/include/boost/numeric/conversion/detail/meta.hpp:30:13: instantiated from 'boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u> >' /work/loc1/boost_1_44_0/include/boost/mpl/if.hpp:67:11: instantiated from 'boost::mpl::if_<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u> >, boost::mpl::identity<boost::numeric::convdetail::get_subranged_BuiltIn2BuiltIn<unsigned char, int> >, boost::mpl::eval_if<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)1u> >, boost::mpl::identity<boost::mpl::identity<boost::numeric::convdetail::subranged_BuiltIn2Udt<unsigned char, int> > >, boost::mpl::if_<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)2u> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Udt2BuiltIn<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Udt2Udt<unsigned char, int> > > > >' /work/loc1/boost_1_44_0/include/boost/mpl/eval_if.hpp:37:41: instantiated from 'boost::mpl::eval_if<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u> >, boost::mpl::identity<boost::numeric::convdetail::get_subranged_BuiltIn2BuiltIn<unsigned char, int> >, boost::mpl::eval_if<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)1u> >, boost::mpl::identity<boost::mpl::identity<boost::numeric::convdetail::subranged_BuiltIn2Udt<unsigned char, int> > >, boost::mpl::if_<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)2u> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Udt2BuiltIn<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Udt2Udt<unsigned char, int> > > > >' /work/loc1/boost_1_44_0/include/boost/numeric/conversion/detail/meta.hpp:82:9: instantiated from 'boost::numeric::convdetail::ct_switch4<mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)1u>, mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)2u>, boost::numeric::convdetail::get_subranged_BuiltIn2BuiltIn<unsigned char, int>, boost::mpl::identity<boost::numeric::convdetail::subranged_BuiltIn2Udt<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Udt2BuiltIn<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Udt2Udt<unsigned char, int> > >' /work/loc1/boost_1_44_0/include/boost/numeric/conversion/detail/udt_builtin_mixture.hpp:45:9: instantiated from 'boost::numeric::convdetail::for_udt_builtin_mixture<mpl_::integral_c<boost::numeric::udt_builtin_mixture_enum, (boost::numeric::udt_builtin_mixture_enum)0u>, boost::numeric::convdetail::get_subranged_BuiltIn2BuiltIn<unsigned char, int>, boost::mpl::identity<boost::numeric::convdetail::subranged_BuiltIn2Udt<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Udt2BuiltIn<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Udt2Udt<unsigned char, int> > >' /work/loc1/boost_1_44_0/include/boost/numeric/conversion/detail/is_subranged.hpp:206:11: [ skipping 9 instantiation contexts ] /work/loc1/boost_1_44_0/include/boost/xpressive/regex_compiler.hpp:281:13: instantiated from 'boost::xpressive::detail::sequence<BidiIter> boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::parse_alternates(FwdIter&, FwdIter) [with FwdIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, RegexTraits = boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> >, CompilerTraits = boost::xpressive::compiler_traits<boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> > >]' /work/loc1/boost_1_44_0/include/boost/xpressive/regex_compiler.hpp:212:75: instantiated from 'boost::xpressive::basic_regex<BidiIter> boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::compile_(FwdIter, FwdIter, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type, std::forward_iterator_tag) [with FwdIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, RegexTraits = boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> >, CompilerTraits = boost::xpressive::compiler_traits<boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> > >, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type = boost::xpressive::regex_constants::syntax_option_type]' /work/loc1/boost_1_44_0/include/boost/xpressive/regex_compiler.hpp:120:60: instantiated from 'boost::xpressive::basic_regex<BidiIter> boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::compile(InputIter, InputIter, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type) [with InputIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, RegexTraits = boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> >, CompilerTraits = boost::xpressive::compiler_traits<boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> > >, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type = boost::xpressive::regex_constants::syntax_option_type]' /work/loc1/boost_1_44_0/include/boost/xpressive/regex_compiler.hpp:129:71: instantiated from 'typename boost::disable_if<boost::is_pointer<InputRange>, boost::xpressive::basic_regex<BidiIter> >::type boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::compile(const InputRange&, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type) [with InputRange = std::basic_string<char>, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, RegexTraits = boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> >, CompilerTraits = boost::xpressive::compiler_traits<boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> > >, typename boost::disable_if<boost::is_pointer<InputRange>, boost::xpressive::basic_regex<BidiIter> >::type = boost::xpressive::basic_regex<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> > >, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type = boost::xpressive::regex_constants::syntax_option_type]' /work/loc1/boost_1_44_0/include/boost/xpressive/basic_regex.hpp:193:61: instantiated from 'static boost::xpressive::basic_regex<BidiIter> boost::xpressive::basic_regex<BidiIter>::compile(const InputRange&, boost::xpressive::basic_regex<BidiIter>::flag_type) [with InputRange = std::basic_string<char>, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, boost::xpressive::basic_regex<BidiIter>::flag_type = boost::xpressive::regex_constants::syntax_option_type]' boost_regex_test.cpp:9:57: instantiated from here /work/loc1/boost_1_44_0/include/boost/mpl/aux_/integral_wrapper.hpp:73:96: warning: the result of the conversion is unspecified because '-0x00000000000000001' is outside the range of type 'boost::numeric::udt_builtin_mixture_enum' [-Wconversion] /work/loc1/boost_1_44_0/include/boost/mpl/aux_/integral_wrapper.hpp: In instantiation of 'mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>': /work/loc1/boost_1_44_0/include/boost/numeric/conversion/detail/meta.hpp:30:13: instantiated from 'boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u> >' /work/loc1/boost_1_44_0/include/boost/mpl/if.hpp:67:11: instantiated from 'boost::mpl::if_<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u> >, boost::mpl::identity<boost::numeric::convdetail::get_subranged_Int2Int<unsigned char, int> >, boost::mpl::eval_if<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)1u> >, boost::mpl::identity<boost::mpl::identity<boost::numeric::convdetail::subranged_Int2Float<unsigned char, int> > >, boost::mpl::if_<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)2u> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Float2Int<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Float2Float<unsigned char, int> > > > >' /work/loc1/boost_1_44_0/include/boost/mpl/eval_if.hpp:37:41: instantiated from 'boost::mpl::eval_if<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u> >, boost::mpl::identity<boost::numeric::convdetail::get_subranged_Int2Int<unsigned char, int> >, boost::mpl::eval_if<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)1u> >, boost::mpl::identity<boost::mpl::identity<boost::numeric::convdetail::subranged_Int2Float<unsigned char, int> > >, boost::mpl::if_<boost::numeric::convdetail::equal_to<mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)2u> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Float2Int<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Float2Float<unsigned char, int> > > > >' /work/loc1/boost_1_44_0/include/boost/numeric/conversion/detail/meta.hpp:82:9: instantiated from 'boost::numeric::convdetail::ct_switch4<mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)1u>, mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)2u>, boost::numeric::convdetail::get_subranged_Int2Int<unsigned char, int>, boost::mpl::identity<boost::numeric::convdetail::subranged_Int2Float<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Float2Int<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Float2Float<unsigned char, int> > >' /work/loc1/boost_1_44_0/include/boost/numeric/conversion/detail/int_float_mixture.hpp:63:9: instantiated from 'boost::numeric::convdetail::for_int_float_mixture<mpl_::integral_c<boost::numeric::int_float_mixture_enum, (boost::numeric::int_float_mixture_enum)0u>, boost::numeric::convdetail::get_subranged_Int2Int<unsigned char, int>, boost::mpl::identity<boost::numeric::convdetail::subranged_Int2Float<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Float2Int<unsigned char, int> >, boost::mpl::identity<boost::numeric::convdetail::subranged_Float2Float<unsigned char, int> > >' /work/loc1/boost_1_44_0/include/boost/numeric/conversion/detail/is_subranged.hpp:184:35: [ skipping 10 instantiation contexts ] /work/loc1/boost_1_44_0/include/boost/xpressive/regex_compiler.hpp:281:13: instantiated from 'boost::xpressive::detail::sequence<BidiIter> boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::parse_alternates(FwdIter&, FwdIter) [with FwdIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, RegexTraits = boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> >, CompilerTraits = boost::xpressive::compiler_traits<boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> > >]' /work/loc1/boost_1_44_0/include/boost/xpressive/regex_compiler.hpp:212:75: instantiated from 'boost::xpressive::basic_regex<BidiIter> boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::compile_(FwdIter, FwdIter, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type, std::forward_iterator_tag) [with FwdIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, RegexTraits = boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> >, CompilerTraits = boost::xpressive::compiler_traits<boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> > >, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type = boost::xpressive::regex_constants::syntax_option_type]' /work/loc1/boost_1_44_0/include/boost/xpressive/regex_compiler.hpp:120:60: instantiated from 'boost::xpressive::basic_regex<BidiIter> boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::compile(InputIter, InputIter, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type) [with InputIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, RegexTraits = boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> >, CompilerTraits = boost::xpressive::compiler_traits<boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> > >, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type = boost::xpressive::regex_constants::syntax_option_type]' /work/loc1/boost_1_44_0/include/boost/xpressive/regex_compiler.hpp:129:71: instantiated from 'typename boost::disable_if<boost::is_pointer<InputRange>, boost::xpressive::basic_regex<BidiIter> >::type boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::compile(const InputRange&, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type) [with InputRange = std::basic_string<char>, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, RegexTraits = boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> >, CompilerTraits = boost::xpressive::compiler_traits<boost::xpressive::regex_traits<char, boost::xpressive::cpp_regex_traits<char> > >, typename boost::disable_if<boost::is_pointer<InputRange>, boost::xpressive::basic_regex<BidiIter> >::type = boost::xpressive::basic_regex<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> > >, boost::xpressive::regex_compiler<BidiIter, RegexTraits, CompilerTraits>::flag_type = boost::xpressive::regex_constants::syntax_option_type]' /work/loc1/boost_1_44_0/include/boost/xpressive/basic_regex.hpp:193:61: instantiated from 'static boost::xpressive::basic_regex<BidiIter> boost::xpressive::basic_regex<BidiIter>::compile(const InputRange&, boost::xpressive::basic_regex<BidiIter>::flag_type) [with InputRange = std::basic_string<char>, BidiIter = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, boost::xpressive::basic_regex<BidiIter>::flag_type = boost::xpressive::regex_constants::syntax_option_type]' boost_regex_test.cpp:9:57: instantiated from here /work/loc1/boost_1_44_0/include/boost/mpl/aux_/integral_wrapper.hpp:73:96: warning: the result of the conversion is unspecified because '-0x00000000000000001' is outside the range of type 'boost::numeric::int_float_mixture_enum' [-Wconversion]

2 1

[filesystem] boost::filesystem::copy
by Tim Blechmann 09 Dec '11

09 Dec '11

hi all, is there any reason, why boost::filesystem v3 does not provide the copy function? it seems to be implemented in namespace boost::filesystem3, but it is not pulled into namespace boost::filesystem. thanks, tim

2 1

mail quotes color coding
by Maxim Yanchenko 09 Dec '11

09 Dec '11

Hi Boosters, If you're using one of web-based mailing list web-sites (like GMane or Google Groups), you may find this GreaseMonkey script useful: http://userscripts.org/scripts/show/92919 It adds coloring of different levels of quotation similar to lists.boost.org. Enjoy! Maxim

1 0

[Regex] Calling convention for _MANAGED code still somewhat broken when mixing native and managed projects
by Martin B. 09 Dec '11

09 Dec '11

Hi there! Background ---------- The header boost/regex/config.hpp currently contains the following code: #if defined(BOOST_MSVC) && (BOOST_MSVC >= 1200) && defined(_MSC_EXTENSIONS) #if defined(_DEBUG) || defined(__MSVC_RUNTIME_CHECKS) || defined(_MANAGED) # define BOOST_REGEX_CALL __cdecl #else # define BOOST_REGEX_CALL __fastcall #endif # define BOOST_REGEX_CCALL __cdecl #endif the `|| defined(_MANAGED)` was added in 2006 (SVN history) to cater for the fact that __fastcall does not work on managed C++/CLI (/clr compiled) projects. See, e.g. this: http://lists.boost.org/boost-users/2004/12/9203.php Problem ------- This is really quite suboptimal, as with the solution as posted above, you need *a separate* lib/dll for managed-C++ and native-C++ Projects. Especially for the DLL, this is a non-solution, as I can only have one DLL for projects/modules that are used in the same application. _MANAGED is a define set by the VC compiler if the /clr switch is present, therefore it is actually never set when compiling the boost libraries. Of course you can set it via `define=_MANAGED` and you can then use these generated libraries from a C++/CLI project. (Which I have done: ... `define=_MANAGED` ... --with-regex ...) BUT: You can now *not* use these libraries from a non-managed ("native") C++ project as that, obviously, doesn't have _MANAGED set, and unlike with the boost build, I don't think it's feasible to define this wholesale for a native project. (And anyways, I'm rather hesitant to define this myself.) Obviously, I could just edit regex/config.hpp, but that is a maintenance nightmare of its own here. Solution -------- I *think* what really would be needed would be a define that the user could specify, something like this: #if defined(_DEBUG) || ... || defined(BOOST_REGEX_NO_FASTCALL) # define BOOST_REGEX_CALL __cdecl ... (I have attached a patch, hope this works.) Would this make sense? To add a short rationale: We use C++/CLI projects as bridges between managed and native modules of our application. In the C++ part, we use boost regexes, and sometimes it would make sense to reuse some native code in a C++/CLI bridge module. If this native code uses Boost.Regex, this doesn't work currently, as the native code file will also be compiled with /clr, and then we have a calling convention mismatch and can't use our boost-regex-dll. cheers, Martin

2 2

[1.49.0] Schedule finalized
by Beman Dawes 08 Dec '11

08 Dec '11

The 1.49.0 schedule has been posted to the Boost C++ Libraries calendar. Milestones (all dates are Mondays): December 19: 1.49.0 (I.E. branches/release) Closed for new libraries. December 26: Quality checks begin January 9: Closed for major changes January 16: Closed for all changes January 23: Beta target date February 20: Release target date The longer period between the beta and release is intended to allow more time to respond to problem reports. --The Release Team

1 0

[msm] deferral stack overfolw
by Richard Szabo 08 Dec '11

08 Dec '11

Hi Christophe just playing around with event deferral I have found a problem which leads to a stack overflow it ends in an infinite loop if I want to defer 2 events in the same state. see attached example it somehow similar to the problem we had earlier but that was fixed ... I have ran this test on MSM trunk version from yesterday. Cheers Richie

2 8

[build] Little help required
by Antony Polukhin 08 Dec '11

08 Dec '11

Hi, I need to create Jamfile.v2 where one of the tests must be compiled on MSVC compilers with additional flag /Zc:wchar_t- How shall I change the following lines: test-suite conversion : # A lot of [ run ... ] lines [ run lexical_cast_typedefed_wchar_test.cpp ../../test/build//boost_unit_test_framework/<link>static ] # Requires /Zc:wchar_t- ; Best regards, Antony Polukhin

2 4

Re: [boost] Boost.Math and Math Constants
by Brent Spillner 08 Dec '11

08 Dec '11

On Wed, 7 Dec 2011 15:33:21 Paul A. Bristow wrote: >John Maddock has now added a new cunning feature that allows the vast majority of users who just >want a built-in double to get the constants quickly as plain variables. So in non-template code, >users can write > > using boost::math::double_constants; > double area = pi * r * r; > >and users can read the equations easily. > >(Float and long double are similarly available in their own namespaces). It's a little bit of work up front, but if you define a custom type with separate overloads for each arithmetic operator/operand type combination (i.e. *(float), *(double), +(float), +(double), etc.) you should be able to offer a single namespace with constants that auto-promote (or demote) to the right type in expressions. That's also easily extensible to user-defined storage classes such as an extended precision float, and I think it's more maintainable since the using declaration (which is now untyped) can't get out of sync with the usage context. To prevent ambiguous overloads (in contexts where the constant itself is supplied as an argument to a polymorphic function, not in expressions), you can leave just one type (perhaps double) as implicitly castable-to, with explicit casts for the others. That seems more Boost-y to me, at any rate.

4 3

[stl_ext_adv] ] Interest in advanced data structures
by Vadim Stadnik 08 Dec '11

08 Dec '11

Hi all, Advanced data structures (ADS) offer useful STL extensions that are not possible or not efficient with basic data structures, such as arrays, linked lists and red-black trees. The project https://github.com/vstadnik/stl_ext_adv http://dl.dropbox.com/u/51041088/stl_ext_adv_doc/index.html focuses mainly on a generalized and unified computer representation of sequences using the augmented B+ trees. It provides the following STL extensions: - The sequence container supports random access iterators and a union of interfaces of STL containers: vector, list and deque. This sequence offers the advantage of efficient update operations with logarithmic running time compared with linear running time of the same operations of std::vector. - The associative containers (set, multiset, map and multimap) with random access iterators. - The enhanced random access iterators effectively address the fundamental problem of the iterator invalidation. - The function accumulate() with logarithmic computational complexity can significantly improve performance of many practically important algorithms and applications, such as the numerical integration, the statistics, the data analysis etc. The examples demonstrate how to improve the computational complexity from O(N) to O(log N) in the following applications and problems: - numerical integration. - calculation of mean value and standard deviation; - calculation of weighted mean value; - testing if any number of consecutive elements are equal; - counting intersections of one interval with sequence intervals; Is there an interest in this project and implemented STL extensions? Interest in potentially useful, but not yet implemented algorithms and specialized containers: 1. The function accumulate() with constant computational cost. With this function some user algorithms, such as the numerical integration, can come close to the absolute theoretical limit of the computational cost. The function can be implemented through iterators enhanced with functionality of accumulators. For more details, see the section “Random access iterators” in the documentation. 2. The functions sequence::splice() with logarithmic running time in the worst case. Note that functions std::list::splice() provide in many cases constant computational cost, however, in the worst case the cost is linear. 3. Any other potentially useful specialized containers, iterators or algorithms? Augmented B+ trees are versatile and powerful data structures. They can be designed to maximize efficiency of particular algorithms and programming solutions. The limitation of specialized containers is that the computational cost of some other operations may increase. About augmented red black trees. The augmented red black trees can also support various STL extensions. The red black trees are yet out of the scope of this project for the reasons explained in the documentation. However, historically augmented red-black trees are probably the first ADS that could extend STL, since the method of augmenting red black trees was described as early as in 1990 [T.H. Cormen, C.E. Leiserson and R.L. Rivest.” Introduction to Algorithms” (1st ed.). MIT Press and McGraw-Hill, 1990]. This means, in particular, that the very first version of STL could provide associative containers with random access iterators. Also, as I understand the previously submitted project https://github.com/boost-vault/Containers/blob/master/countertree.zipimplem… containers based on the augmented red black trees. It is hardly possible to make an exact prediction, but without a doubt future versions of STL will benefit from advanced data structures. Regards, Vadim Stadnik

11 29

boost.heap in trunk
by Tim Blechmann 07 Dec '11

07 Dec '11

hi all, i've imported my boost.heap library into trunk. it currently won't compile with gcc, but i've submitted patches against boost.parameter [1] and boost.fusion [2]. i hope they are applied, soon. i managed to integrate it into the documentation system, but it still needs to be integrated into the bug tracker and the regression test system. can i do that myself? tim [1] https://svn.boost.org/trac/boost/ticket/6214 [2] https://svn.boost.org/trac/boost/ticket/6215

3 2

Re: [boost] c++11 and gcc 4.7
by Leo Goodstadt 07 Dec '11

07 Dec '11

> > From: Bruce Adams <tortoise_74(a)yahoo.co.uk> > Date: Tue, 6 Dec 2011 19:08:56 +0000 (GMT) > > Hi, > I am attempting to do a cost benefit analysis to justify adopting the > subset of C++11 that is supported by gcc 4.7. > As threads are one of the biggest features of c++11, I may be asked to > justify just boost.thread vs > gcc 4.7 + boost.thread. You may also wish to consider using a higher level threading library on top of std::thread / boost::thread. We have been using Intel Threading Building Blocks (http://threadingbuildingblocks.org/) for a while now, and it seems to live very happily alongside Boost. TBB means that you don't have to roll your own thread pools, or adjust the parallelism each time your programme is run. It is also a very thin layer in terms of efficiency. The modern trend across many programming languages also seems to move away from using (manual) synchronisation primitives whenever possible (just as "raw" new and delete has become rare in c++ over the past 20 years). TBB allows complex pipelines to be supported quite naturally in terms of a data flow. My only reservation is that it requires dynamic linking, which is not always desirable or even possible. Finally, the extra level of abstraction in TBB probably means that the onus on supporting varying standards of c++ 11 conformance falls on Intel and not you or your company! Leo

1 0

Is there any interest in a library which solves C++ class reflection feature just like Java does?
by jinhua luo 07 Dec '11

07 Dec '11

Hi, In brief, I'd designed and implemented somehow C++ class reflection based on boost libraries. It has some unique advantages: a) it doesn't require code generator b) platform independent and compiler independent (I tested it on Windows and Linux, with vs2008 and gcc respectively) c) it's non-intrusive for the class definition, instead, you just need to declare and describe your class via some straightforward macros anywhere (header file or source file, and may be within any namespace), which also means you can wrap an external third-party library (which you have no way to touch the source codes) and reflects it classes. d) Cross shared library boundary, you can dynamic load the shared library and reflect the classes within it, without need to export any symbol manunally in C wrapper function way e) the API looks like Java reflection API Below is some codes snippet to have an overview of this library: -----libTest.cpp---start--- #include <iostream> #include <string> #include <boost/reflection/reflection.hpp> namespace test { class AccountItf { public: virtual std::string getId() const = 0; virtual void setId(std::string id) = 0; }; #define ACCOUNT_INTERFACE_REFL_DECLARE \ BOOST_REFL_INTERFACE(test::AccountItf) \ BOOST_REFL_CONST_METHOD(getId, std::string()) \ BOOST_REFL_METHOD(setId, void(std::string)) class Account : public AccountItf { std::string id; public: Account() : age(0) {} Account(std::string id, unsigned int age) : id(id), age(age) {} static void echo(Account* acct, std::string banner) { std::cout << banner + ": " << acct->getId() << std::endl; } std::string getId() const { return id; } void setId(std::string id) { this->id = id; } public: unsigned int age; }; //Account declaration for used by reflection //this declaration can be placed anywhere, even the header file BOOST_REFL_CLASS ( (test)(Account), //constructors BOOST_REFL_CONSTRUCTOR() BOOST_REFL_CONSTRUCTOR(std::string id, unsigned int age) //static methods BOOST_REFL_STATIC_METHOD(echo, void (Account* acct, std::string banner)) //properties BOOST_REFL_PROPERTY(age, unsigned int) //derived Inteface ACCOUNT_INTERFACE_REFL_DECLARE ) } -----libTest.cpp----end-- Compile the libTest.cpp into the libTest.dll or libTest.so. -----main.cpp----start-- #include <iostream> #include <string> using namespace std; #include <boost/reflection/reflection.hpp> using namespace boost::reflection; #if defined(BOOST_WINDOWS) #include <Windows.h> #else #include <dlfcn.h> #endif int main(int argc, char* argv[]) { #if defined(BOOST_WINDOWS) LoadLibraryA (argv[1]); #else dlopen(argv[1], RTLD_NOW); #endif Class t = Class::forName("test.Account"); boost::any obj = t.newInstance(std::string("Account-id-100"), (unsigned int)26); t.invokeStatic("echo", obj, std::string("TEST")); TypeInfoArray tArray; tArray.push_back(BOOST_REFL_TYPEID(std::string)); Method m1 = t.getMethod("setId", tArray); m1.invoke(obj, std::string("Account-id-200")); Method m2 = t.getMethod("getId"); boost::any ret = m2.invoke(obj); std::cout << "Account getId(): " << boost::any_cast<std::string>(ret) << std::endl; Property prop = t.getProperty("age"); prop.set(obj, (unsigned int)30); std::cout << "Account age: " << boost::any_cast<unsigned int>(prop.get(obj)) << std::endl; return 0; } -----main.cpp---end--- Compile the main.cpp into the executable and execute it: ./main libTest.dll it will output: TEST: Account-id-100 Account getId(): Account-id-200 Account age: 30 This library is very useful for framework-level design which needs C++ reflection, e.g. recently I'm working on somehow SQL mapping library for C++, just like MyBatis, and reflection makes possible to invoke the getter/setter of the object instances of classes specified in the XML file. Regards, JinHua

8 25

c++11 and gcc 4.7
by Bruce Adams 06 Dec '11

06 Dec '11

Hi, I am attempting to do a cost benefit analysis to justify adopting the subset of C++11 that is supported by gcc 4.7. I believe there is a strong case for doing so from just the minor features and library improvements. However, I am having a hard time putting together a convincing cost benefit analysis (actually I would like to be able to do this with parts of boost too - any help with this would be great). I have many subjective arguments for boost, C++11 and TR1 but am tasked with trying to justifying any change in terms of costs and benefits. One of Boost's roles is to fill in gaps in c++ support where compiler vendors have not yet provided an implementation. I know that g++4.7 has incomplete support for multi-threading but it is unclear whether this is in the core language area and/or library area and what platforms it applies to. I am specifically interested in GNU/Linux. The status of boost for gcc4.7 is unclear (I know it has not been officially released yet but the status for gcc 4.6.2 is also unclear). Both of the following links from www.boost.org are several years and versions out of date http://www.boost.org/doc/libs/1_34_0/status/compiler_status.html http://boost.sourceforge.net/regression-logs/ Will boost.thread work as a drop in replacement for std::thread or is anything missing or broken on the core language side? (On the gcc side I am also interested in whether std::thread is a sufficiently complete implementation of the standard that boost.thread might not be necessary). The answer to this question may make my work harder. I was asked to justifiy either TR1, some part of boost or C++11 as my preference. I opted for C++11 as the most useful. I would probably have to justify boost libraries on a case by case basis. Justifying use of C++11 actually amounts to justifying a compiler upgrade + possibly training + possibly boost.thread As threads are one of the biggest features of c++11, I may be asked to justify just boost.thread vs gcc 4.7 + boost.thread. Surprisingly another thing that is unclear is the exact set of boost libraries that were included in C++11. I don't have either the standard (other than the February draft http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3242.pdf) or a good summary of the standard to hand. Suprisingly neither the boost website nor the g++ page have a list either, though the following two links are helpful: http://www.boost.org/doc/libs/1_48_0/?view=filtered_std-tr1 http://www.boost.org/doc/libs/1_48_0/?view=filtered_std-proposal I found a reference somewhere online (that I can no longer find) claiming, I believe incorrectly, that boost file_system is in C++11. This isn't mentioned on: http://www.boost.org/doc/libs/1_48_0/libs/filesystem/v3/doc/index.htm But nor its is presence in the 2005 "TR2" proposal. I worry that the 2005 TR2 proposal may be confused with any real TR2 proposal following on from C++11. I note that boost.chrono claims to be implemnting C++11 but I would have thought it was other way around and that the boost library was incorporated into the standard. http://www.boost.org/doc/libs/1_48_0/doc/html/chrono.html Anyway, the closest I've come to a list of libraries in C++11 outside of n3242 is: http://www2.research.att.com/~bs/C++0xFAQ.html#library Regards, Bruce.

3 2

Re: [boost] Is there any interest in a library which solves C++ class reflection feature just like Java does?
by Brian Wood 06 Dec '11

06 Dec '11

Matus Chochlik on Tue, Dec 6, 2011 at 2:40 AM, jinhua luo <ljh.home.king(a)gmail.com> wrote: > Hi, > Hi, >> It has some unique advantages: >> a) it doesn't require code generator > Good, but it is not so unique Because C++ compiler is a code generator? [ ...] >> d) Cross shared library boundary, you can dynamic load the shared library >> and reflect the classes within it, without need to export any symbol >> manunally in C wrapper function way > I believe (and I have some expertise in using and implementing reflection > in C++ to base that belief upon) that the basic reflection should > compile-time and any run-time reflection should be built on top > of that. Agreed. -- Brian Wood Ebenezer Enterprises http://webEbenezer.net <http://webebenezer.net/> (651) 251-9384

1 0

[chrono] steady_clock efficiency
by Kenneth Porter 06 Dec '11

06 Dec '11

I expect most people will use boost::chrono::steady_clock to measure performance. I've been considering switching from my raw calls to the Windows peformance counter APIs to the steady_clock. I'm a little worried about the overhead of what should be a non-intrusive facility. In examing the source, I see that steady_clock::now() reads the performance counter and then multiplies it by the reciprocal of the counter's frequency (acquired on first use of the clock) to return the time in nanoseconds. How expensive is this 64 bit multiply on a 32 bit system? How hard would it be to have now() return a time_point that stores the raw tick value and only converts it to nanoseconds when a calculation in real units is required? (Comparison to another time_point could still be done in performance counter ticks, saving the multiply.) Is it worth the extra complexity to demand-convert ticks to nanoseconds? Source is in boost_1_48_0\boost\chrono\detail\inlined\win\chrono.cpp

5 15

Status of ISO/IEC TR 24733 library idea?
by Mateusz Łoskot 06 Dec '11

06 Dec '11

Hi, There is ISO/IEC TR 24733 draft on decimal floating-point arithmetic. I found old thread by Stefan Slapeta: Decimal floating point library [1] I wonder, what is status of this idea in Boost? [1] http://lists.boost.org/Archives/boost/2006/02/101457.php Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

3 5

[release] Is Rlease branch is open for merge?
by Artyom Beilis 06 Dec '11

06 Dec '11

Hello, Is release brunch is open for merge of updates from trunk? Artyom Beilis -------------- CppCMS - C++ Web Framework: http://cppcms.sf.net/ CppDB - C++ SQL Connectivity: http://cppcms.sf.net/sql/cppdb/

2 2

disable_if conundrum
by Marshall Clow 05 Dec '11

05 Dec '11

I have a function that returns a pair of iterators. There's also a version that takes a comparison predicate. template<class ForwardIterator, class Compare> std::pair<ForwardIterator, ForwardIterator> foo ( ForwardIterator first, ForwardIterator last ); template<class ForwardIterator, class Compare> std::pair<ForwardIterator, ForwardIterator> foo ( ForwardIterator first, ForwardIterator last, Compare comp ); I want to provide a range-based version of it. template<class Range> std::pair<typename boost::range_iterator<const Range>::type, typename boost::range_iterator<const Range>::type> foo ( const Range &r ); template<class Range, class Compare> std::pair<typename boost::range_iterator<const Range>::type, typename boost::range_iterator<const Range>::type> foo ( const Range &r, Compare comp ); Ok. There's a problem. If I call: foo ( first, last ) I get an error, because there are two perfectly good two argument candidates. Fine. Been there, seen that. I can use disable_if to make sure that the second range based version is only "active" when the arguments are different types. It's verbose, but it (usually) works template<class Range, class Compare> typename boost::disable_if_c<boost::is_same<Range, Compare>::value, std::pair<typename boost::range_iterator<const Range>::type, typename boost::range_iterator<const Range>::type> >::type foo ( const Range &r, Compare comp ); But this time it does not! I get a compile error telling me that the compiler can't deal with boost::range_iterator<XXX>::type, when XXX = some random iterator. It seems that the compiler wants to evaluate all the parameters of disable_if_c before deciding whether or not to SFINAE it (I guess that's not unreasonable, but it's not what I want) Apparently, all the other times that I did this, the return type of the function was not a dependent type of the template arguments. Any suggestions for a workaround here? -- Marshall -- 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

4 9

[enable_if] compile failure in trunk
by Tim Blechmann 05 Dec '11

05 Dec '11

trying to merge boost.heap into trunk, there is one issue, which seems to be triggered by the enable_if in the boost.heap testsuite. compiling with gcc (4.5 or 4.6), i get the following error: In file included from /home/tim/workspace/boost-trunk/boost/parameter.hpp:17:0, from /home/tim/workspace/boost-trunk/boost/heap/policies.hpp:12, from /home/tim/workspace/boost-trunk/boost/heap/detail/stable_heap.hpp:20, from /home/tim/workspace/boost_heap/libs/heap/test/../../../boost/heap/fibonacci_heap.hpp:20, from /home/tim/workspace/boost_heap/libs/heap/test/fibonacci_heap_test.cpp:8: /home/tim/workspace/boost-trunk/boost/parameter/name.hpp:52:1: error: template argument 2 is invalid In file included from /home/tim/workspace/boost-trunk/boost/fusion/support/detail/segmented_fold_until_impl.hpp:20:0, from /home/tim/workspace/boost-trunk/boost/fusion/sequence/intrinsic/detail/segmented_begin_impl.hpp:15, from /home/tim/workspace/boost-trunk/boost/fusion/sequence/intrinsic/detail/segmented_begin.hpp:10, from /home/tim/workspace/boost-trunk/boost/fusion/sequence/intrinsic/begin.hpp:17, from /home/tim/workspace/boost-trunk/boost/fusion/container/vector/vector10.hpp:15, from /home/tim/workspace/boost-trunk/boost/fusion/container/vector/vector_fwd.hpp:14, from /home/tim/workspace/boost-trunk/boost/fusion/container/vector/vector.hpp:10, from /home/tim/workspace/boost-trunk/boost/fusion/tuple/tuple.hpp:11, from /home/tim/workspace/boost-trunk/boost/fusion/tuple.hpp:10, from /home/tim/workspace/boost-trunk/boost/fusion/include/tuple.hpp:10, from /home/tim/workspace/boost-trunk/boost/math/tools/tuple.hpp:89, from /home/tim/workspace/boost-trunk/boost/math/special_functions/detail/igamma_inverse.hpp:13, from /home/tim/workspace/boost-trunk/boost/math/special_functions/gamma.hpp:1543, from /home/tim/workspace/boost-trunk/boost/math/special_functions/detail/bessel_jy.hpp:14, from /home/tim/workspace/boost-trunk/boost/math/special_functions/bessel.hpp:17, from /home/tim/workspace/boost-trunk/boost/math/special_functions.hpp:18, from /home/tim/workspace/boost-trunk/boost/random/generate_canonical.hpp:22, from /home/tim/workspace/boost-trunk/boost/random.hpp:52, from /home/tim/workspace/boost_heap/libs/heap/test/mutable_heap_tests.hpp:1, from /home/tim/workspace/boost_heap/libs/heap/test/fibonacci_heap_test.cpp:12: /home/tim/workspace/boost-trunk/boost/fusion/iterator/equal_to.hpp:77:9: error: expected nested-name-specifier before ‘enable_if’ /home/tim/workspace/boost-trunk/boost/fusion/iterator/equal_to.hpp:77:18: error: expected initializer before ‘<’ token /home/tim/workspace/boost-trunk/boost/fusion/iterator/equal_to.hpp:88:9: error: expected nested-name-specifier before ‘enable_if’ /home/tim/workspace/boost-trunk/boost/fusion/iterator/equal_to.hpp:88:18: error: expected initializer before ‘<’ token /home/tim/workspace/boost-trunk/boost/fusion/iterator/equal_to.hpp:98:31: error: ‘boost::fusion::iterator_operators::operator==’ has not been declared /home/tim/workspace/boost-trunk/boost/fusion/iterator/equal_to.hpp:99:31: error: ‘boost::fusion::iterator_operators::operator!=’ has not been declared In file included from /home/tim/workspace/boost-trunk/boost/fusion/iterator/segmented_iterator.hpp:13:0, from /home/tim/workspace/boost-trunk/boost/fusion/sequence/intrinsic/detail/segmented_begin.hpp:11, from /home/tim/workspace/boost-trunk/boost/fusion/sequence/intrinsic/begin.hpp:17, from /home/tim/workspace/boost-trunk/boost/fusion/container/vector/vector10.hpp:15, from /home/tim/workspace/boost-trunk/boost/fusion/container/vector/vector_fwd.hpp:14, from /home/tim/workspace/boost-trunk/boost/fusion/container/vector/vector.hpp:10, from /home/tim/workspace/boost-trunk/boost/fusion/tuple/tuple.hpp:11, from /home/tim/workspace/boost-trunk/boost/fusion/tuple.hpp:10, from /home/tim/workspace/boost-trunk/boost/fusion/include/tuple.hpp:10, from /home/tim/workspace/boost-trunk/boost/math/tools/tuple.hpp:89, from /home/tim/workspace/boost-trunk/boost/math/special_functions/detail/igamma_inverse.hpp:13, from /home/tim/workspace/boost-trunk/boost/math/special_functions/gamma.hpp:1543, from /home/tim/workspace/boost-trunk/boost/math/special_functions/detail/bessel_jy.hpp:14, from /home/tim/workspace/boost-trunk/boost/math/special_functions/bessel.hpp:17, from /home/tim/workspace/boost-trunk/boost/math/special_functions.hpp:18, from /home/tim/workspace/boost-trunk/boost/random/generate_canonical.hpp:22, from /home/tim/workspace/boost-trunk/boost/random.hpp:52, from /home/tim/workspace/boost_heap/libs/heap/test/mutable_heap_tests.hpp:1, from /home/tim/workspace/boost_heap/libs/heap/test/fibonacci_heap_test.cpp:12: /home/tim/workspace/boost-trunk/boost/fusion/container/list/cons.hpp:91:22: error: expected nested-name-specifier before ‘disable_if’ /home/tim/workspace/boost-trunk/boost/fusion/container/list/cons.hpp:91:32: error: expected ‘,’ or ‘...’ before ‘<’ token /home/tim/workspace/boost-trunk/boost/fusion/container/list/cons.hpp:122:18: error: expected nested-name-specifier before ‘disable_if’ /home/tim/workspace/boost-trunk/boost/fusion/container/list/cons.hpp:122:28: error: expected initializer before ‘<’ token compiling with gcc against 1.48 works fine. clang++ correctly compiles this code against boost-trunk. any idea, what could go wrong there? thanks, tim

2 2