- Boost - lists.boost.org

[iostreams][1.33.1] Re: possible code_converter bug?
by Jonathan Turkanis 12 Oct '05

12 Oct '05

[Doug, I think I'd like to fix this problem. The noconv case is not covered by the regression test; if it were, this problem would have been noticed before] Niklas Wiberg wrote: > Hi, > Sorry for mailing you privately, but this feels a bit too detailed to > bother the list readers with... I don't mind your writing me privately, but we discuss lots of detailed things on the list, and someone else might have some good insight. With your permission, I'll post this to the list. > I'm using a "null codecvt" as described at > http://www.codeproject.com/vcpp/stl/upgradingstlappstounicode.asp?df=100&fo… > > together with code_converter. > > In code_converter<Device, Codevt, Alloc>::write(), there is a piece of > code for handling noconv results: > case codecvt_base::noconv: > { > // This can be shortened to two memcpy's. > const char* c = (const char*) (s + total); > for ( std::size_t index = 0; > index < sizeof(intern_type); > index += sizeof(extern_type), > ++buf.ptr() ) > { > memcpy(buf.ptr(), c + index, sizeof(extern_type)); > if (buf.eptr() == buf.end()) > buf.flush(dev()); > } > ++total; > } > > eptr() is never increased. Can that be correct? > If I debug and look at the call to buffer::flush() (which is called when > my stream is flushed, not by this code), I can see that > streamsize amt = static_cast<std::streamsize>(eptr_ - ptr_); > results in amt being negative since ptr_ is larger than eptr_. > Perhaps that's why I don't get anything in my file? This code probably doesn't do what I wanted it to do, but it turns out it doesn't matter, since there's a more fundamental problem. When I wrote this, I was working from the 1998 standard; in the 2003 edition, the role of noconv was clarified, as follows: result do_out(stateT& state, const internT* from, const internT* from_end, const internT*& from_next, externT* to, externT* to_limit, externT*& to_next) const; result do_in(stateT& state, const externT* from, const externT* from_end, const externT*& from_next, internT* to, internT* to_limit, internT*& to_next) const; .... If returns noconv, internT and externT are the same type and the converted sequence is identical to the input sequence [from, from_next). As a result, the NullCodecvt in the article you cite should never be returning noconv, since wchar_t != char. The next version of code_converter will handle noconv correctly, and may also be more correct in other respects. Unfortunately, it will have to wait for 1.34. > Niklas Wiberg -- Jonathan Turkanis www.kangaroologic.com

1 0

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

12 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-12T14:19:18Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 868 failures in 6 libraries: graph (1) iostreams (1) parameter (3) python (6) range (3) serialization (854) |graph| graphviz_test: cw-9_4 |iostreams| gzip_test: gcc-4_0-darwin |parameter| sfinae: vc-6_5 vc-6_5-stlport unnamed: vc-7_1 |python| pointer_vector: cw-9_4 try: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux vector_indexing_suite: cw-9_4 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_delete_pointer_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_demo_polymorphic: gcc-3_4_3-sunos test_demo_polymorphic_dll: gcc-3_4_3-sunos test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_deque_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_deque_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_diamond_binary_archive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_binary_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_text_archive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_text_warchive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_diamond_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_xml_archive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_xml_warchive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_list_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_list_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_map_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: gcc-3_4_3-sunos test_polymorphic_binary_archive_dll: gcc-3_4_3-sunos test_polymorphic_text_archive: gcc-3_4_3-sunos test_polymorphic_text_archive_dll: gcc-3_4_3-sunos test_polymorphic_text_warchive: gcc-3_4_3-sunos test_polymorphic_text_warchive_dll: gcc-3_4_3-sunos test_polymorphic_xml_archive: gcc-3_4_3-sunos test_polymorphic_xml_archive_dll: gcc-3_4_3-sunos test_polymorphic_xml_warchive: gcc-3_4_3-sunos test_polymorphic_xml_warchive_dll: gcc-3_4_3-sunos test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_set_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_set_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: intel-win32-8_1 vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux test_variant_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_vector_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1

1 0

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

12 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-12T05:00:23Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 101 failures in 11 libraries: concept_check (13) graph (2) mpl (1) parameter (13) python (1) serialization (36) spirit (8) thread (4) tuple (1) type_traits (1) typeof (21) |concept_check| stl_concept_covering: cw-9_4 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 gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tricky_abstract_type_test: intel-win32-9_0 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4

1 0

Boost::Ruby
by Alan Gutierrez 12 Oct '05

12 Oct '05

Is there any interest? -- Alan Gutierrez - alan(a)engrm.com - http://engrm.com/blogometer/

14 36

[tools][bcp] using boost internally in other libraries
by Bjørn Roald 12 Oct '05

12 Oct '05

Hi boosters, In the following I have made the assumption that it is in the spirit of the Boost license for Boost to be used as foundation for other libraries, open-source, free, commercial, or whatever. In addition, that any modifications to the libraries is allowed for any such purpose. However, it is my belief that most of the developers would not like to see extensive branching in the effort of providing better Boost libraries. This would most likely stretch the potential of the C++ community in providing a better future set of standard libraries for the language. So to my main subject: I have been working for some time to get acceptance for using Boost libraries as elements in a higher level portable platform for library development. It has surprised me how hard it is to make compelling and attractive set of arguments for using Boost (or other libraries) without attempting to ignore some pretty serious concerns. These concerns are: - commercial support for our use of Boost - quality assurance of Boost itself - stability of Boost API - maintainability of Boost source code - deployability of our library into environments using different versions of Boost or libraries used in boost - configuration management issues in general for us and our customers - platform support in Boost ( or if the platform support Boost if you like ;-) All of these concerns can be declared acceptable, given that you are willing to accept trade offs and risk. The issue I try to raze is if it is possible to reduce the magnitude of these risks and trade offs. One of the key issues is that you have to decide on some strategy of how to maintain your boost version. The most obvious strategy may be to stay with the latest Boost release at any time, this will however add risk as you have to adopt new changes as they are introduced into Boost and not as it fits your own release plans. The obvious alternative is to stay with a Boost release longer, possibly until you are forced to switch. This strategy will quickly force you into maintaining your own branch as Boost developers can not be expected to support old releases. Between these there are many shades of gray which may fit more or less well depending on your project and your customers. If your customers themselves use boost you are likely to meet a added configuration management, testing and release related cost and risk. As library developers have a very different type of customer relationship than what is the case for end application developers there are a number of concerns that make adaptation of Boost, or any other 3rd party library for that sake, more problematic for library developers. The main issue is to what degree a library depends on other libraries and hence introduces indirect or direct dependencies to its users. These dependencies tend to be troublesome for the library developer to support, as well as they may be troublesome for users to accept. In fact users may easily be in situations where such dependencies are completely unacceptable. To help to understand the issue I like to define categories of libraries which affect the degree they are affected by these concerns. Cat1. open source, source distributions, allowing encapsulation Cat2. open source, source distributions in general Cat3. open source, binary distributions Cat4. closed source Cat1 and Cat2 are build-able source code distributions. This give the user the ability to build the library and ensure that it is built correctly with other library it depends on, on the target system. Cat1 add to this the ability to hide the use of it inside other libraries, i.e. it can live concurrently in an end system with other versions of the same Cat1 library. Cat3 and Cat4 are for this discussion as far as I can tell similar. Cat3 may be called open source by some, but if for a variation of reasons rebuild by user is not an option, the results in this discussion becomes the same. Boost is a Cat2 library. Even if the extensive use of headers only libraries help some of the issues addressed in this post, it is not a general solution that makes Boost or part of Boost a Cat1 library. Now an example showing some dependencies: MyCustomersApplication |---- Boost 1.33 |---- MyLib |---- Boost 1.32 If MyLib is Cat1 or Cat2 the chances are good that we may be ok. Most likely MyLib will soon adopt the migration to new Boost releases by the actions of the maintainer or by patches from end users. If however MyLib is Cat 3 or 4 we have a problem. This problem is real even if the use of Boost in MyLib is strictly internal. In my view this is an especially bad problem. Even if I do not intend to use Boost in any way in the API of MyLib I still have this issue of incompatibility. This problem will disqualify use of Boost even internally for many library developers. Now, if we assume (which in most cases is dangerous) that library developers are a skilled race among the general population of the C++ community, it is in my view sad that many of them are not able to use Boost or potentially participate professionally in the efforts to improve Boost. I am sure many actually would participate if they could use it at work. Any management with commercial goals mixed with good sense of business would also let their developers participate actively, especially if this was the best way of maintaining parts of their product. This would let their developers focus their effort on the parts of the product that is core to their business rather than the parts that can be found and downloaded on the net (read boost.org) Ok, back to the example. If MyLib have no intention of using Boost in the API, is there a way? I have been struggling with this issue for a while. The obvious solution to me is to make Boost a Cat1, the problem is how? As mentioned earlier in many threads on this list header-only libraries helps, however this does not apply to all of Boost and it is possibly other issues that I am not aware of. If we look at the C++ domain in general, there are limited ways of hiding symbols in libraries. As far as I can see, none of these are sufficiently powerful to hide boost completely. One alternative is however to let the symbols leak, but make sure none are in conflict with the other version of boost. Some sort of namespace replacement or wrapping comes to my mind. Side Note: I am aware of symbol encapsulation abilities in windows DLLs and similar new features supported by GCC, however these are not generally supported on all platforms, so I have selected to ignore them. They may however be helpful to many. The general idea is that there are no references to symbols in the boost namespace between any MyLib libraries, nor in any header files in or referenced from MyLib API. How can this be achieved? I have concluded that accessing boost trough namespace wrapping header files are unpractical at best. This needs to be designed into all of boost for this to work, and I do not know exactly how. The main challenge is #include <boost/xxxx.hpp> directives which does not refer to the wrapping headers. An alternative is to replace all references to boost namespace with e.g. MyLib::boost namespace in the boost source code and change all #include <boost/xxx.hpp> directives to #include <Mylib/boost/xxx.hpp>. This would make a buildable library which would not share symbols with other versions of boost. The result is a branch or clone if you like of Boost that can be used with the same effect as if we actually had a Cat1 boost library. There is however serious problems here. Any management with common sense would say.... hey.... stop. The prospect of undertaking maintenance of a branch or clone of Boost does not make much sense --- So, the only way this would work is to make it possible to maintain the library in the boost community and somehow make the translation to the MyLib/boost namespace a pure production step. In configuration management terms this means that the original or possibly slightly patched boost source code is under configuration control along with a tool-chain used under MyLib system build that transforms the boost source tree to the form used internally. This is where I started looking at Boost tools/bcp. The bcp (boost copy I guess) tool is an excellent starting point since it already has the ability to copy selected libraries and their dependencies from the boost distribution to project specific source tree. So in a sense it is similar in spirit, but solves primarily a different goal, which is to reduce the size of the boost distribution imported. This is complementary to what I want. I have experimented a little with some extensions to bcp using some simple regexp replace calls and got some encouraging results. I am able to build the resulting source tree using only small adjustments to top level bjam files after treatment by the modified bcp. I have yet to complete support for replacing boost with nested namespaces since it is trickier to do the replacement of the ending braces of the namespace scope. I believe other tools than the Regexp library may be more appropriate for this task. So to wrap up: I do not believe anything prevents me from going along this path if I decide to do so. I am however interested in the boost developers attitude toward this approach, and in particular if this is something you will encourage and/or support. I am willing to work on the tool support for this in boost or to maintain a modified bcp tool if that is more appropriate. Regards Bjørn Roald

9 24

Problem building boost regex on hpux - getlocale(int) problem
by Navdeep Shergill 12 Oct '05

12 Oct '05

Hi all I am trying to build boost v 1.30.0 regex library on a hp machine. The 'syname' output is this: PA-RISC2.0_hpux_11.00_v5.1c I go to the "boost-1.30.0/libs/regex/build" directory and issue a 'make -f gcc.mak' command. I get the following errors: ../src/c_regex_traits.cpp:660: call of overloaded `getlocale(int)' is ambiguous /usr/gcc/3.1/lib/gcc-lib/hppa2.0w-hp-hpux11.00/3.1/include/locale.h:144: candidates are: locale_data* getlocale(int) ../src/c_regex_traits.cpp:62: const char* <unnamed>::getlocale(int) ../src/c_regex_traits.cpp:663: call of overloaded `getlocale(int)' is ambiguous /usr/gcc/3.1/lib/gcc-lib/hppa2.0w-hp-hpux11.00/3.1/include/locale.h:144: candidates are: locale_data* getlocale(int) ../src/c_regex_traits.cpp:62: const char* Here is the gcc version. Its v3.1 =========================================================== [4:00pm: regex/build]gcc -v Reading specs from /usr/intel/pkgs/gcc/3.1/lib/gcc-lib/hppa2.0w-hp-hpux11.00/3.1/specs Configured with: ../gcc-3.1/configure --host=hppa2.0w-hp-hpux11.00 --target=hppa2.0w-hp-hpux11.00 --prefix=/usr/gcc/3.1 --enable-languages=c,c++ --enable-threads --with-gnu-as --with-as=/usrgcc/3.1/bin/gas Thread model: single gcc version 3.1 [4:03pm: regex/build] ============================================================= Anyone have any idea how I can fix this problem of the ambiguious getlocale function? Thanks!

2 2

Short Mailing List Outage on Thursday 10/13
by Jeff Garland 12 Oct '05

12 Oct '05

FYI --------------------------- I am sorry for this short notice but I need to reboot milliways to upgrade its firmware. It will be down for about 1 hour Thursday morning (10/13). - 6:00am-7:00am Pacific US time - 7:00am-8:00am Mountain US time - 8:00am-9:00am Central US time - 9:00am-10:00am Eastern US time - 1:00pm-2:00pm GMT Specifically, the following services provided by the OSL will be unavailable during this timeframe: - All e-mail services - Incoming mail (including all mailman list hosting) - Outgoing mail (including all mailman list hosting) - IMAP/SSL - All web hosting - lists.boost.org - ...and all others hosted by the OSL

1 0

Is there PGI & PathScale compiler support?
by Ryo IGARASHI 12 Oct '05

12 Oct '05

Hi developpers, Are no boost user using PGI or PathScale compiler on AMD x86_64 machines? There seems to be no toolset support for both compilers yet. Are they bad compilers when using boost libraries? -- Ryo IGARASHI rigarash(a)gmail.com

1 0

Re: [boost] Please look at my suggested pimpl library in the file vault.
by Asger Mangaard 12 Oct '05

12 Oct '05

I've uploaded an updated version ... >> Pavel Vozenilek wrote ... > I do have a few. > /Pavel > > ________________________________________________ > 1. You should not use double underscores > (and neither leading single underscore). > These are reserved for standard. > It's corrected. > ________________________________________________ > 2. It is better when member functions are all > lowercase (like elsewhere in Boost). > > It's corrected. > ________________________________________________ > 3. pimpl.hpp: > > The base::_Get() should have > BOOST_ASSERT() before dereferencing. > > Possibly this function could be omitted > altogether since it is always overriden. > It's corrected. > ----------- > > _Destructor should be named destroy() > to evoke action. > > Better yet, move it into real destructor. > It's corrected. > ----------- > > late_creation policy may nam named "manual_creation" > or so. > > The Set() should destroy previous instance > if non-NULL. > > The _Get() should contain > BOOST_ASSERT() or throw if NULL. > It's corrected. > --------------- > > Closing bracket for namespace should nopt have ";" > but should have comment like // namespace pimpl_policies > It's corrected. > ---------------- > > operator=() does shallow copy of dynamically > allocated value. Is this really what ypu want? > It's corrected. > ________________________________________________ > 4. Compiling with Intel C++ 7.0 for Windows > I get error: > > testsuite.cpp > C:\work\reviews\pimpl\testsuite.cpp(54): error: no suitable user-defined > conversion from "boost::pimpl<CMyValues1, > > boost::pimpl_policies::base>" to "const boost::pimpl<CMyValues2, > boost::pimpl_policies::late_creation>" exists > test.m_ValuesWithLazyCreator2 = test.m_ValuesWithDefaultConstructor; > I've now tested with Intel C++ 9.0 windows and it works fine. How can I get a copy of this old version? > ________________________________________________ > 5. The pimpl doesn't show how I work with > member functions. This is the most important part > of the idiom and If there's way to make the tedious > work any simpler I am all for it. > You just work with the pimpl's -> operator. That will give you access to the pimpl's member functions. The new 'testsuite.cpp' shows its use. And thanks for your corrections, I highly appreciate them. Regards, Asger Mangaard

10 22

[regex, C++ Committee Meeting] any progress on lwg issue #523?
by Eric Niebler 12 Oct '05

12 Oct '05

Was library issue 523: "regex case-insensitive character ranges are unimplementable as specified" discussed at the committee meeting? http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#523 -- Eric Niebler Boost Consulting www.boost-consulting.com

2 1