September 2005 - Boost - lists.boost.org

[Serialization] Pointer to const
by Loïc Joly 12 Sep '05

12 Sep '05

Hello everybody, There a still many stuff I do not understand how to do with boost::serialization. One of them is the following : Let's say I have the following classes : struct B { int i; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & i;} }; struct A { B const *pc; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & pc; } }; When I try to serialize a A, I get the following error (MSVC8 beta 2): c:\boost\include\boost-1_33\boost\archive\detail\iserializer.hpp(474) : error C2440: 'reinterpret_cast' : cannot convert from 'const B **__w64 ' to 'void **' Conversion loses qualifiers c:\boost\include\boost-1_33\boost\archive\detail\iserializer.hpp(471) : while compiling class template member function 'void boost::archive::detail::load_pointer_type<Archive,Tptr>::invoke(Archive &,Tptr &)' with [ Archive=boost::archive::text_iarchive, Tptr=const B * ] Of course, if I replace B const *pc by B *pc, then the code works correctly.What can I do to serialize pointers to const data ? Regards, -- Loïc

2 4

[gmane web interface] why is the latest artivle from the 8th of sep????
by Thorsten Ottosen 12 Sep '05

12 Sep '05

The headline pretty much says it all. Without an up to date web interface, I can't post stuff :-( br -Thorsten

2 1

Boost regression notification (2005-09-12 [RC_1_33_0])
by Douglas Gregor 12 Sep '05

12 Sep '05

<html> <head> <meta http-equiv="refresh" content="1; url=issues-email.txt"> </head> <body> <p>Update in progress (building archive index, done in approximately 6 seconds), please wait...</p> </body> </html>

1 0

Boost regression notification (2005-09-03 [HEAD])
by Douglas Gregor 12 Sep '05

12 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-03T05:00:17Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. typeof Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 85 failures in 11 libraries: foreach (6) graph (4) math (6) mpl (2) multi_index (5) parameter (4) serialization (40) spirit (2) thread (8) typeof (4) wave (4) |foreach| user_defined: cw-8_3 cw-9_4 msvc vc-6_5 vc-6_5-stlport vc-7_0 |graph| graphviz_test: vc-7_1 vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |math| octonion_test: gcc-4_0-darwin gcc-4_0-darwin quaternion_test: gcc-4_0-darwin gcc-4_0-darwin special_functions_test: gcc-4_0-darwin gcc-4_0-darwin |mpl| size_t: gcc-4_0-darwin gcc-4_0-darwin |multi_index| test_capacity: gcc-4_0-darwin test_list_ops: gcc-4_0-darwin test_modifiers: gcc-4_0-darwin test_safe_mode: gcc-4_0-darwin test_update: gcc-4_0-darwin |parameter| basics: borland-5_6_4 macros: borland-5_6_4 sfinae: borland-5_6_4 unnamed: borland-5_6_4 |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_barrier_lib: intel-9.0-linux test_condition_lib: intel-9.0-linux test_mutex_lib: intel-9.0-linux test_once_lib: intel-9.0-linux test_read_write_mutex_lib: intel-9.0-linux test_thread_lib: intel-9.0-linux test_tss_lib: intel-9.0-linux test_xtime_lib: intel-9.0-linux |typeof| type_emulation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux type_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: gcc-3.3.6-linux intel-9.0-linux

4 4

Boost regression notification (2005-09-12 [HEAD])
by Douglas Gregor 12 Sep '05

12 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-12T05:00:07Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. typeof format concept_check Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 256 failures in 17 libraries: algorithm/string (1) concept_check (11) date_time (44) filesystem (16) foreach (7) format (3) graph (25) iostreams (1) math (6) mpl (2) parameter (4) regex (36) serialization (40) spirit (2) thread (24) typeof (29) wave (5) |algorithm/string| regex: gcc-3_3-darwin |concept_check| stl_concept_covering: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 |date_time| testc_local_adjustor: gcc-2.95.3-linux testclock: gcc-2.95.3-linux testdate: gcc-2.95.3-linux testdate_dll: gcc-2.95.3-linux testdate_duration: gcc-2.95.3-linux testdate_duration_dll: gcc-2.95.3-linux testdate_input_facet: gcc-2.95.3-linux testdate_input_facet_dll: gcc-2.95.3-linux testdate_iterator: gcc-2.95.3-linux testdate_iterator_dll: gcc-2.95.3-linux testdst_rules: gcc-2.95.3-linux testdst_transition_day_rule: gcc-2.95.3-linux testduration: gcc-2.95.3-linux testfiletime_functions: gcc-2.95.3-linux testformatters: gcc-2.95.3-linux testformatters_dll: gcc-2.95.3-linux testgenerators: gcc-2.95.3-linux testgenerators_dll: gcc-2.95.3-linux testgreg_cal: gcc-2.95.3-linux testgreg_cal_dll: gcc-2.95.3-linux testgreg_day: gcc-2.95.3-linux testgreg_day_dll: gcc-2.95.3-linux testgreg_duration_operators: gcc-2.95.3-linux testgreg_durations: gcc-2.95.3-linux testgreg_durations_dll: gcc-2.95.3-linux testgreg_month: gcc-2.95.3-linux testgreg_month_dll: gcc-2.95.3-linux testgreg_serialize_xml: vc-7_1 testgreg_year: gcc-2.95.3-linux testgreg_year_dll: gcc-2.95.3-linux testiterator: gcc-2.95.3-linux testlocal_adjustor: gcc-2.95.3-linux testlocal_time_iterator: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc testlocal_time_period: gcc-2.95.3-linux msvc testmicrosec_time_clock: gcc-2.95.3-linux testparse_time: gcc-2.95.3-linux testperiod: gcc-2.95.3-linux testperiod_dll: gcc-2.95.3-linux testtime: gcc-2.95.3-linux testtime_formatters: gcc-2.95.3-linux testtime_period: gcc-2.95.3-linux |filesystem| convenience_test: gcc-3_4_3-sunos msvc default_name_check_test: gcc-3_4_3-sunos msvc fstream_test: gcc-3_4_3-sunos msvc large_file_support_test: gcc-3_4_3-sunos msvc operations_test: gcc-3_4_3-sunos msvc operations_test_dll: gcc-3_4_3-sunos msvc path_test: gcc-3_4_3-sunos msvc path_test_dll: gcc-3_4_3-sunos msvc |foreach| user_defined: cw-8_3 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-6_5-stlport vc-7_0 |format| format_test2: vc-7_1 format_test3: vc-7_1 format_test_wstring: vc-7_1 |graph| betweenness_centrality_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux gcc-3_4_3-sunos mingw-3_4_2 dag_longest_paths: gcc-3.4.4-linux gcc-3_4_3-sunos mingw-3_4_2 dijkstra_cc: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux gcc-3_4_3-sunos mingw-3_4_2 dijkstra_heap_performance: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux gcc-3_4_3-sunos mingw-3_4_2 graphviz_test: vc-7_1 vc-7_1 vc-7_1 layout_test: intel-win32-9_0 relaxed_heap_test: gcc-3.4.4-linux gcc-3_4_3-sunos mingw-3_4_2 |iostreams| regex_filter_test: gcc-3_3-darwin |math| octonion_test: gcc-4_0-darwin gcc-4_0-darwin quaternion_test: gcc-4_0-darwin gcc-4_0-darwin special_functions_test: gcc-4_0-darwin gcc-4_0-darwin |mpl| size_t: gcc-4_0-darwin gcc-4_0-darwin |parameter| basics: borland-5_6_4 macros: borland-5_6_4 sfinae: borland-5_6_4 unnamed: borland-5_6_4 |regex| bad_expression_test: gcc-3_3-darwin captures_example: gcc-3_3-darwin captures_test: gcc-3_3-darwin collate_info: gcc-3_3-darwin concept_check: gcc-3_3-darwin credit_card_example: gcc-3_3-darwin grep: gcc-3_3-darwin icu_example: gcc-3_3-darwin mfc_example: gcc-3_3-darwin object_cache_test: gcc-3_3-darwin partial_regex_grep: gcc-3_3-darwin partial_regex_match: gcc-3_3-darwin posix_api_check: gcc-3_3-darwin posix_api_check_cpp: gcc-3_3-darwin recursion_test: gcc-3_3-darwin regex_config_info: gcc-3_3-darwin regex_dll_config_info: gcc-3_3-darwin regex_grep_example_1: gcc-3_3-darwin regex_grep_example_2: gcc-3_3-darwin regex_grep_example_3: gcc-3_3-darwin regex_grep_example_4: gcc-3_3-darwin regex_iterator_example: gcc-3_3-darwin regex_match_example: gcc-3_3-darwin regex_merge_example: gcc-3_3-darwin regex_regress: gcc-3_3-darwin regex_regress_dll: gcc-3_3-darwin regex_replace_example: gcc-3_3-darwin regex_search_example: gcc-3_3-darwin regex_split_example_1: gcc-3_3-darwin regex_split_example_2: gcc-3_3-darwin regex_timer: gcc-3_3-darwin regex_token_iterator_eg_1: gcc-3_3-darwin regex_token_iterator_eg_2: gcc-3_3-darwin static_mutex_test: gcc-3_3-darwin msvc wide_posix_api_check_cpp: gcc-3_3-darwin |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_barrier: msvc test_barrier_lib: intel-9.0-linux msvc test_condition: msvc test_condition_lib: intel-9.0-linux msvc test_mutex: msvc test_mutex_lib: intel-9.0-linux msvc test_once: msvc test_once_lib: intel-9.0-linux msvc test_read_write_mutex: msvc test_read_write_mutex_lib: intel-9.0-linux msvc test_thread: msvc test_thread_lib: intel-9.0-linux msvc test_tss: msvc test_tss_lib: intel-9.0-linux msvc test_xtime: msvc test_xtime_lib: intel-9.0-linux msvc |typeof| template_int_emulation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux template_int_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 template_tpl_emulation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux template_tpl_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 msvc template_type_emulation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux template_type_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 type_emulation: borland-5_6_4 cw-8_3 cw-9_4 cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux type_native: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: gcc-3.3.6-linux gcc-3_4_3-sunos intel-9.0-linux

1 0

Problem with Serialization and Building with Managed Extensions
by Jared McIntyre 12 Sep '05

12 Sep '05

I am trying to use boost::serialization in a managed code (CLR) project in Visual Studio. The area that serialization is being used, and all the objects that are being serialized, and standard C++. There are no managed objects related to the serialization process. In fact, I have a test app that reproduces the problem that can be built and run without managed extensions on. But, if I turn building with managed extensions on, several parts of the of the serialization templates turn up missing at link time. I get several errors like the following: LINK : error LNK2020: unresolved token (0A00013F) std._Uninitialized_fill_n<class boost::variant<class TestClass,int,float,double,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boos LINK : error LNK2020: unresolved token (0A000158) std._Uninit_fill_n<class boost::variant<class TestClass,int,float,double,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::detail::variant::void_,struct boost::deta Also, during build, the compiler doesn't like the use of __fastcall in several areas of the code. For example: ..\..\..\..\boost\boost_1_33_0\boost\type_traits\detail\is_mem_fun_pointer_tester.hpp(2443) : warning C4561: '__fastcall' incompatible with the '/clr' option: converting to '__stdcall' I don't know if these are related. I'm using VS 7.1. Does anyone have any thoughts on what I should look at from here? Thanks, Jared McIntyre

1 0

Massive Spamming of the boost Wiki
by Peter Schmitteckert (boost) 12 Sep '05

12 Sep '05

Dear All, sadly, the Boost wiki is currently spammed with a big amount of spam, see e.g. <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?RecentChanges> Since the IP adress is logged, I'd like to ask wether there's a possibility for action. I'm reporting this, because if the spamming continues on this level the wiki will be rendered useless soon. Best regards, Peter

6 7

Re: [boost] read_write_mutex fundamentally broken in 1.33?
by russell＠eminence.com.au 12 Sep '05

12 Sep '05

>>The trouble is what do we do with 1.33.1? We could either revert to the >>1.32 version (if that is actually reliable, the current regression tests >>don't show up these problems so we don't really know), or we could yank >> it >>out of Boost entirely. I'm leaning towards yanking it out at present, >> but >>it's a drastic step, and this presupposes that the original authors of >> the >>class can't temporarily fix things for 1.33.1 (they all look to have >> either >>gone away or be too busy at present however). >> >>What do other folks think? >> >> >> > I don't know either whether someone relies on the presence of rw mutex > being in the > boost. However if he/she is using it, the usage itself is dangerous > anyhow. The company I am working for is actually using timed rw mutex on a current project (and they seem to be working), so I for one would like them to stay in. I suspect timed locks aren't going to deadlock? > In my opinion it is better to omit it until it is fixed. > > I am also not in the mood to dig through the sources to find out how the > design was > intended to work. I would also vote for basing the design on a > theoretically sound > ground (not claiming the current is not) that is understandable too. > > While trying to find out the reason for the initial reported bug I found > myself in a > maze of hard to understand details. Perhaps it would even be better not > to base > the rw mutex on level 0 primitives only, but write it to the native API > of the > respective platform? How should we proceed from here? Should the community come up with a list of alternative implementations that could be evaluated and used as a starting point? Or do we need to go back a step further and decide what types of mutexes or primitives are actually desired?

7 9

Any interest in a chart library
by Schrom, Brian T 12 Sep '05

12 Sep '05

I've been working on a charting library for a few weeks and am wondering whether their would be any interest in having a boost one. I'm not even sure that it makes sense for boost, as it seems a higher level library than most of libraries and also unrelated to other libraries. There would be many things to work out, like no graphics in Boost (that I'm aware of), my not being an expert C++ person, etc, so I'm just trying to get a feel whether it is worth pursuing more here or not, or if there would be another forum that would be better. By charting library, I mean something that you can give data to and that it plots it in a view port, with axis, labels, title etc like you would get with Excel charts, Gnu Plot, Pro-Essentials, etc Thanks, Brian

8 9

File Vault broken
by Eric Niebler 12 Sep '05

12 Sep '05

I just noticed that *everything* in the file vault is gone: http://boost-sandbox.sf.net/vault What's up? -- Eric Niebler Boost Consulting www.boost-consulting.com

6 15