- Boost - lists.boost.org

[Marketing] Quote on front page?
by Doug Gregor 23 Jul '05

23 Jul '05

The Spirit page (http://spirit.sourceforge.net/) has a quote on its front page, which I find appealing. So I stole the idea and added the C++ Coding Standards quote (which is, perhaps, the most flattering of the few we've collected) to the Boost front page header. The effect can be seen here: http://www.osl.iu.edu/~dgregor/boost/index.htm Opinions? Should this go into the front page? Doug

7 7

Home page adjustments?
by David Abrahams 23 Jul '05

23 Jul '05

The boxes on the right side of the new home page design look like they should be closer together, to me, rather than lined up with the various sections of the left-hand text. Especially when the page is a comfortably narrow width, the Groups/Contribute box ends up too far down. -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 3

[boost-users] [date_time] length of generic periods
by Friedrich Wilckens 23 Jul '05

23 Jul '05

Hi, the concept of the length of generic periods puzzles me. The "normal" case p.length() = p.end() - p.begin() makes sense to me, but why is a period with last() == begin() treated as a special case, having length 0? Having this special case make the length concept behave strangely. For example, [2005-May-1/2005-May-1] has length 0, but [2005-May-1/2005-May-2] has length 2! Actually there is no period of length 1 at all. As I understand from the documentation, the philosophical reason behind this seems to be that the end points of periods are considered "points" and that a point and therefore a period that consists of a single point has zero extension. This sounds plausible if you think of the periods like intervals on the real number line. But our situation is different, I think, since we always deal with discrete quantities that have a finite length (or "duration"). I would interpret the period [2005-May-1/2005-May-1] as the time period that lasts during the whole day 2005-May-1, from 00:00 up to 23:59:59.999... Therefore, I would give it the length (duration) 1. [2005-May-1/2005-Apr-30] would accordingly be an empty period of length 0, and [2005-May-1/2005-Apr-29] would be an invalid period of length -1. The length of a date_period p would then be simply the number of days in p, multiplied with the unit of the duration_type. The template parameter duration_type can be used to defined different measurements of the length. In the standard case (duration of a day is 1) you measure the period length in days. But you could also measure it in seconds, by using a duration_type with unit() = 86400. What do you think about this? Sincerely, Friedrich

2 3

Boost regression notification (2005-07-23)
by Douglas Gregor 23 Jul '05

23 Jul '05

Boost regression test failures ------------------------------ Report time: 2005-07-23T15:34:21Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 168 failures in 9 libraries: assign (2) filesystem (4) multi_index (38) program_options (4) random (2) serialization (105) test (5) thread (1) wave (7) |assign| multi_index_container: cw-9_5-darwin gcc-3_4_3-sunos |filesystem| operations_test_dll: borland-5_6_4 mingw-3_4_2 path_test_dll: borland-5_6_4 mingw-3_4_2 |multi_index| test_basic: cw-9_5-darwin gcc-3_4_3-sunos test_capacity: cw-9_5-darwin gcc-3_4_3-sunos test_comparison: cw-9_5-darwin gcc-3_4_3-sunos test_composite_key: cw-9_5-darwin gcc-3_4_3-sunos test_conv_iterators: cw-9_5-darwin gcc-3_4_3-sunos test_copy_assignment: cw-9_5-darwin gcc-3_4_3-sunos test_hash_ops: cw-9_5-darwin gcc-3_4_3-sunos test_iterators: cw-9_5-darwin gcc-3_4_3-sunos test_list_ops: cw-9_5-darwin gcc-3_4_3-sunos test_modifiers: cw-9_5-darwin gcc-3_4_3-sunos test_mpl_ops: cw-9_5-darwin gcc-3_4_3-sunos test_observers: cw-9_5-darwin gcc-3_4_3-sunos test_projection: cw-9_5-darwin gcc-3_4_3-sunos test_range: cw-9_5-darwin gcc-3_4_3-sunos test_safe_mode: cw-9_5-darwin gcc-3_4_3-sunos test_set_ops: cw-9_5-darwin gcc-3_4_3-sunos test_special_list_ops: cw-9_5-darwin gcc-3_4_3-sunos test_special_set_ops: cw-9_5-darwin gcc-3_4_3-sunos test_update: cw-9_5-darwin gcc-3_4_3-sunos |program_options| cmdline_test_dll: mingw-3_4_2 positional_options_test_dll: mingw-3_4_2 unicode_test_dll: cw-9_5-darwin gcc-3_3-darwin |random| random_test: intel-win32-8_1 intel-win32-8_1 |serialization| test_class_info_load_binary_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_binary_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-6_5 test_class_info_load_xml_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_const_load_fail1: borland-5_6_4 test_const_load_fail1_nvp: borland-5_6_4 test_const_load_fail2: borland-5_6_4 test_const_load_fail2_nvp: borland-5_6_4 test_const_save_fail1: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail2: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail3: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_demo_dll: cw-9_4 cw-9_4 test_demo_exception_dll: cw-9_4 cw-9_4 test_demo_fast_archive_dll: msvc vc-6_5 test_demo_pimpl_dll: msvc vc-6_5 vc-7_0 test_demo_portable_archive_dll: borland-5_6_4 intel-win32-8_1 intel-win32-8_1 test_demo_shared_ptr: cw-9_4 cw-9_4 cw-9_5-darwin vc-8_0 test_demo_shared_ptr_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-7_0 test_diamond_binary_archive: cw-8_3 cw-9_5-darwin test_diamond_binary_archive_dll: cw-9_5-darwin test_diamond_text_archive: cw-8_3 cw-9_5-darwin test_diamond_text_archive_dll: cw-9_5-darwin test_diamond_text_warchive: cw-8_3 cw-9_5-darwin test_diamond_text_warchive_dll: cw-9_5-darwin test_diamond_xml_archive: cw-8_3 cw-9_5-darwin test_diamond_xml_archive_dll: cw-9_5-darwin test_diamond_xml_warchive: cw-8_3 cw-9_5-darwin test_diamond_xml_warchive_dll: cw-9_5-darwin test_map_binary_archive_dll: msvc vc-6_5 vc-7_0 test_map_text_archive_dll: msvc vc-6_5 vc-7_0 test_map_text_warchive_dll: msvc vc-6_5 vc-7_0 test_mult_archive_types: cw-9_4 cw-9_4 cw-9_5-darwin test_mult_archive_types_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 test_non_default_ctor_text_archive_dll: cw-9_5-darwin test_non_default_ctor_text_warchive_dll: cw-9_5-darwin test_non_default_ctor_xml_archive_dll: cw-9_5-darwin test_non_default_ctor_xml_warchive_dll: cw-9_5-darwin test_non_intrusive_text_archive_dll: cw-9_5-darwin test_non_intrusive_text_warchive_dll: cw-9_5-darwin test_non_intrusive_xml_archive_dll: cw-9_5-darwin test_non_intrusive_xml_warchive_dll: cw-9_5-darwin |test| errors_handling_test: cw-9_5-darwin test_fp_comparisons: borland-5_6_4 test_tools_test: cw-9_4 cw-9_4 cw-9_5-darwin |thread| test_thread_lib: mingw-3_4_2 |wave| test_re2c_lexer: vc-8_0 test_slex_lexer: vc-8_0 testwave: cw-8_3 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux vc-8_0

1 0

Re: [boost] [serialization] bug in latest changetoboost/serialization/base_object.hpp
by JOAQUIN LOPEZ MU?Z 23 Jul '05

23 Jul '05

Hello Robert, ----- Mensaje original ----- De: Robert Ramey <ramey(a)rrsd.com> Fecha: Viernes, Julio 22, 2005 3:15 pm Asunto: Re: [boost] [serialization] bug in latest changetoboost/serialization/base_object.hpp > Sorry, I fixed this but I see someone already beat me to it. It was me, I finally managed to grab CVS access yesterday. > > I'll add a compile only test for this. > Thank you! There's still a pending problem with boost/serialization/base_object.hpp in tru64cxx65-042 and como-4_3_3-vc7_1 (both EDG-based): http://tinyurl.com/9a5em http://tinyurl.com/d25mz Basically, the compiler detects at compile time and bans dereferencing a null pointer as it's done in static const void_cast_detail::void_caster & invoke(){ return static_cast<const void_cast_detail::void_caster &>( * static_cast<const void_cast_detail::void_caster *>(NULL) ); } This is the same problem as previously discussed (in other context) in http://article.gmane.org/gmane.comp.lib.boost.devel/126588 The problem is currently breaking all Boost.Serialization tests in the aforementioned toolsets. As this implementation has been recently included to cope with some CW problems, maybe an easy workaround is to have it only for that platform, and revert to the previous "static void invoke" interface for other toolsets. Another alternative (not tested) could be resorting to a dummy non-null pointer: static const void_cast_detail::void_caster & invoke(){ static const void_cast_detail::void_caster * dummy_ptr; return * dummy_ptr; } I'm sorry I can't be more helpful, but I'm on a short vacation, away from my development environment (writing this from an Internet café.) Hope this helps a little, though. Good luck, Joaquín M López Muñoz Telefónica, Inevstigación y Desarrollo

1 0

Question about shared_prt doc's
by Joe Gottman 23 Jul '05

23 Jul '05

In the documentation for the shared_ptr constructor that takes a weak_ptr parameter, it says that if the weak_ptr is empty then so is the constructed shared_ptr. But it also says that if the weak_ptr has a use_count() of 0 then a bad_weak_ptr exception is thrown. Since an empty weak_ptr has a use_count() of 0, these statements can't both be true. Which one is? Joe Gottman

2 2

Potentially breaking change in VC8
by Carl Daniel 23 Jul '05

23 Jul '05

Current builds of VC8 (newer than the June CTP) are implementing the change suggested by http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1757.html I don't know how or if this affects any Boost code, but it's something to watch out for. I would expect the next CTP of VC8 may well include this change. -cd PS: The change makes code like this ill-formed: template <unsigned n> struct bit_count { enum { value = n ? bit_count<n >> 1>::value+1 : 0 }; }; template <> struct bit_count<0> { enum { value = 0 }; };

1 0

[parameter] New libraries docs?
by Rene Rivera 22 Jul '05

22 Jul '05

The new Parameter library is not listed in the usual places where new libraries are listed. What's up with that? -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

2 1

Lambda::bind, throw() and VC71
by Richard Crossley 22 Jul '05

22 Jul '05

The following simple example fails to compile with VC71, (OK with Intel 8.1). Is there a workaround for this? Regards, Richard. ---------------------- #include <boost/lambda/bind.hpp> struct S{ void mfn1(){}; void mfn2() throw() {}; }; int main() { using namespace boost::lambda; S s; bind(&S::mfn1,_1)(s); // OK bind(&S::mfn2,_1)(s); // Error with VC71 } ---------------------- cl /c /Od /Gm /EHsc /RTC1 /MLd /Zc:wchar_t /Zc:forScope /GR /ZI /W3 /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /Fo"Debug/" /Fd"Debug/vc70.pdb" /Gd /TP .\TestBind.cpp TestBind.cpp c:\boost\boost\lambda\detail\bind_functions.hpp(220) : error C2664: 'boost::lambda::lambda_functor<T>::lambda_functor(const boost::lambda::lambda_functor<T> &)' : cannot convert parameter 1 from 'boost::lambda::lambda_functor_base<Act,Args>' to 'const boost::lambda::lambda_functor<T> &' with [ T=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda:: function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall S::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits::type,boost::lambda::detail::bind_traits<boost::tup les::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null _type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::t ype,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost ::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda: :detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail:: bind_traits<boost::tuples::null_type>::type>> ] and [ Act=boost::lambda::action<2,boost::lambda::function_action<2>>, Args=boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall S::* const )(void) throw()>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits::type,boost::lambda::detail::bind_traits<boost::tup les::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null _type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::t ype,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost ::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda: :detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail:: bind_traits<boost::tuples::null_type>::type> ] and [ T=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda:: function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall S::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits::type,boost::lambda::detail::bind_traits<boost::tup les::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null _type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::t ype,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost ::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda: :detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail:: bind_traits<boost::tuples::null_type>::type>> ] Reason: cannot convert from 'boost::lambda::lambda_functor_base<Act,Args>' to 'const boost::lambda::lambda_functor<T>' with [ Act=boost::lambda::action<2,boost::lambda::function_action<2>>, Args=boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall S::* const )(void) throw()>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits::type,boost::lambda::detail::bind_traits<boost::tup les::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null _type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::t ype,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost ::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda: :detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail:: bind_traits<boost::tuples::null_type>::type> ] and [ T=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda:: function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall S::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits::type,boost::lambda::detail::bind_traits<boost::tup les::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null _type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::t ype,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost ::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda: :detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail:: bind_traits<boost::tuples::null_type>::type>> ] No constructor could take the source type, or constructor overload resolution was ambiguous c:\Source\TestBind\TestBind.cpp(13) : see reference to function template instantiation 'const boost::lambda::lambda_functor<T> boost::lambda::bind<void(__thiscall S::* )(void),boost::lambda::placeholder1_type>(const Arg1 & ,const Arg2 &)' being compiled with [ T=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda:: function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall S::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits::type,boost::lambda::detail::bind_traits<boost::tup les::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null _type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::t ype,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost ::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda: :detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail:: bind_traits<boost::tuples::null_type>::type>>, Arg1=void (__thiscall S::* )(void), Arg2=boost::lambda::placeholder1_type ]

2 1

[parameter] Tutorial checked in
by David Abrahams 22 Jul '05

22 Jul '05

I think the tutorial documentation is close to complete. Last minute editorial comments would be appreciated. See libs/parameter/doc/html/index.html The best way to make comments is to embed them in a copy of the source: libs/parameter/doc/index.rst and post that. Don't worry about whether I'll miss the comment; I have diff tools ;-) -- Dave Abrahams Boost Consulting www.boost-consulting.com

9 42