July 2004 - Boost - lists.preview.boost.org

[program_options] Need help with remaining fails
by Vladimir Prus 21 Jul '04

21 Jul '04

The current test results: http://tinyurl.com/4ghk7 show just three failures which I'd like to fix other than by marking them expected. Those are options_description_test_dll, on msvc and intel7-vc6, and variable_map_test_dll, on intel7-vc6. They all fail at runtime with memory access violation. Since I don't have vc6, I'd appreciate if someone could look at the failures in a debugger. This is probably some bug in vc6 library, so I hope a single fix will suffice. Thanks in advance, Volodya

4 6

[serialization] 100% pass in latest Mandrake test
by Jeff Garland 21 Jul '04

21 Jul '04

Robert - Things are looking good in my latest round of regression tests, all tests pass, down to a few warnings. Nice work! http://boost.sourceforge.net/regression-logs/cs-LinuxMandrake.html I even included the date_time serialization tests (exercises the code that serializes dates, times, durations, etc) in this run :-) Jeff

1 0

More errors today than yesterday
by Victor A. Wagner Jr. 21 Jul '04

21 Jul '04

This morning's grepped output (full log at ftp://rudbek.com/pub/boost ): ...found 35276 targets... ...using 215 temp targets... ...updating 2890 targets... ...on 100th target... ...on 200th target... ...on 300th target... ...on 400th target... C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'lower' : ambiguous symbol C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'upper' : ambiguous symbol ...failed vc-C++ ..\bin\boost\libs\numeric\ublas\test7.test\vc7.1\debug\test71.obj... C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'lower' : ambiguous symbol C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'upper' : ambiguous symbol ...failed vc-C++ ..\bin\boost\libs\numeric\ublas\test7.test\vc7.1\debug\test72.obj... ...skipped <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.CMD for lack of <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test71.obj... ...skipped <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.exe for lack of <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.CMD... ...on 500th target... ...on 600th target... ...on 700th target... ...on 800th target... ...on 900th target... ...on 1000th target... ...on 1100th target... ...on 1200th target... ...on 1300th target... ..\libs\conversion\test\implicit_cast_fail.cpp(22) : error C2664: 'boost::implicit_cast' : cannot convert parameter 1 from 'const char [7]' to 'boost::mpl::identity<T>::type' ..\libs\conversion\test\implicit_cast_fail.cpp(22) : error C2512: 'foo' : no appropriate default constructor available C:\Projects\boost\boost\function\function_template.hpp(78) : error C2198: 'int (__cdecl *)(float)' : too few arguments for call through pointer-to-function C:\Projects\boost\libs\function\test\function_test_fail1.cpp(22) : error C2451: conditional expression of type 'void' is illegal C:\Projects\boost\libs\function\test\function_test_fail1.cpp(29) : fatal error C1004: unexpected end of file found ..\libs\multi_array\test\fail_ref_cview3.cpp(55) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_cview2.cpp(49) : error C2440: 'initializing' : cannot convert from 'boost::multi_array_ref<T,NumDims>::const_array_view<NDims>::type' to 'boost::detail::multi_array::multi_array_view<T,NumDims>' ..\libs\multi_array\test\fail_ref_cview.cpp(53) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_csubarray3.cpp(50) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_csubarray2.cpp(46) : error C2440: 'initializing' : cannot convert from 'boost::multi_array_ref<T,NumDims>::const_reference' to 'boost::detail::multi_array::sub_array<T,NumDims>' ..\libs\multi_array\test\fail_ref_csubarray.cpp(46) : error C2440: 'initializing' : cannot convert from 'boost::detail::multi_array::multi_array_impl_base<T,NumDims>::const_subarray<NDims>::type' to 'boost::detail::multi_array::sub_array<T,NumDims>' ..\libs\multi_array\test\fail_ref_criterator.cpp(31) : error C2440: 'initializing' : cannot convert from 'boost::reverse_iterator<Iterator>' to 'boost::reverse_iterator<Iterator>' ..\libs\multi_array\test\fail_ref_cparen.cpp(42) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_citerator.cpp(31) : error C2440: 'initializing' : cannot convert from 'boost::detail::multi_array::array_iterator<T,TPtr,NumDims,Reference>' to 'boost::detail::multi_array::array_iterator<T,TPtr,NumDims,Reference>' ...on 1400th target... ..\libs\multi_array\test\fail_ref_cdata.cpp(39) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_cbracket.cpp(42) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_cview3.cpp(57) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_cview2.cpp(52) : error C2440: 'initializing' : cannot convert from 'boost::multi_array_ref<T,NumDims>::const_array_view<NDims>::type' to 'boost::detail::multi_array::multi_array_view<T,NumDims>' ..\libs\multi_array\test\fail_cview.cpp(56) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_csubarray3.cpp(47) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_csubarray2.cpp(43) : error C2440: 'initializing' : cannot convert from 'boost::multi_array_ref<T,NumDims>::const_reference' to 'boost::detail::multi_array::sub_array<T,NumDims>' ..\libs\multi_array\test\fail_csubarray.cpp(44) : error C2440: 'initializing' : cannot convert from 'boost::detail::multi_array::multi_array_impl_base<T,NumDims>::const_subarray<NDims>::type' to 'boost::detail::multi_array::sub_array<T,NumDims>' ..\libs\multi_array\test\fail_criterator.cpp(31) : error C2440: 'initializing' : cannot convert from 'boost::reverse_iterator<Iterator>' to 'boost::reverse_iterator<Iterator>' ..\libs\multi_array\test\fail_cparen.cpp(42) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_citerator.cpp(31) : error C2440: 'initializing' : cannot convert from 'boost::detail::multi_array::array_iterator<T,TPtr,NumDims,Reference>' to 'boost::detail::multi_array::array_iterator<T,TPtr,NumDims,Reference>' ..\libs\multi_array\test\fail_cdata.cpp(40) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_cbracket.cpp(38) : error C2166: l-value specifies const object C:\Projects\boost\boost\detail\typed_in_place_factory.hpp(50) : error C2440: 'initializing' : cannot convert from 'int' to 'const char [3]' C:\Projects\boost\boost\detail\typed_in_place_factory.hpp(50) : fatal error C1903: unable to recover from previous error(s); stopping compilation C:\Projects\boost\boost\detail\in_place_factory.hpp(51) : error C2661: 'A::A' : no overloaded function takes 3 arguments ..\libs\python\test\object_fail1.cpp(10) : error C2039: '_' : is not a member of 'boost::python::api::object' ...on 1500th target... FAIL :: Get time of day micro second clock not supported due to inadequate compiler ...failed execute-test ..\bin\boost\libs\date_time\test\testmicrosec_time_clock.test\vc7.1\debug\testmicrosec_time_clock.run... ...on 1600th target... ...on 1700th target... ...skipped <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.run for lack of <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.exe... ...on 1800th target... ...on 1900th target... ...on 2000th target... ...on 2100th target... ...on 2200th target... ...on 2300th target... ...on 2400th target... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_xml_save.test\vc7.1\debug\test_demo_xml_save.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_xml_load.test\vc7.1\debug\test_demo_xml_load.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_xml.test\vc7.1\debug\test_demo_xml.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_shared_ptr.test\vc7.1\debug\test_demo_shared_ptr.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_exception.test\vc7.1\debug\test_demo_exception.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo.test\vc7.1\debug\test_demo.run... ...on 2500th target... ../libs/thread/test/test_read_write_mutex.cpp(205): error in "test_read_write_mutex": test r1.m_value == 10 failed ...failed execute-test ..\bin\boost\libs\thread\test\test_read_write_mutex.test\vc7.1\debug\threading-multi\test_read_write_mutex.run... ...on 2600th target... ...on 2700th target... ...on 2800th target... **** error return code: -1 ...failed RmTemps ..\bin\boost\libs\test\test\prg_exec_fail4.test\vc7.1\debug\prg_exec_fail4.run... ...failed RmTemps ..\bin\boost\libs\test\test\prg_exec_fail3.test\vc7.1\debug\prg_exec_fail3.run... ...failed RmTemps ..\bin\boost\libs\test\test\prg_exec_fail2.test\vc7.1\debug\prg_exec_fail2.run... **** exception(205): C string: Test error by throwing C-style string exception ...failed RmTemps ..\bin\boost\libs\test\test\prg_exec_fail1.test\vc7.1\debug\prg_exec_fail1.run... ../libs/test/test/test_exec_fail4.cpp(22): error in "call_test_main": Msg Exception in "call_test_main": C string: Test error by throwing C-style string exception ...failed RmTemps ..\bin\boost\libs\test\test\test_exec_fail4.test\vc7.1\debug\test_exec_fail4.run... ../libs/test/test/test_exec_fail3.cpp(23): error in "call_test_main": test v == 2 failed ../libs/test/test/test_exec_fail3.cpp(24): error in "call_test_main": test 2 == v failed ...failed RmTemps ..\bin\boost\libs\test\test\test_exec_fail3.test\vc7.1\debug\test_exec_fail3.run... ../libs/test/test/test_exec_fail2.cpp(25): error in "call_test_main": test v == 2 failed ../libs/test/test/test_exec_fail2.cpp(26): error in "call_test_main": sample BOOST_ERROR call ../libs/test/test/test_exec_fail2.cpp(27): fatal error in "call_test_main": test 2 == v failed ...failed RmTemps ..\bin\boost\libs\test\test\test_exec_fail2.test\vc7.1\debug\test_exec_fail2.run... C:/Projects/boost/libs/test/build/../src/test_main.cpp(40): error in "call_test_main": test test_main_result == 0 || test_main_result == boost::exit_success failed ...failed RmTemps ..\bin\boost\libs\test\test\test_exec_fail1.test\vc7.1\debug\test_exec_fail1.run... ../libs/test/test/ifstream_line_iterator_test.cpp(28): error in "test_default_delimeter": test it != utf::ifstream_line_iterator() failed ../libs/test/test/ifstream_line_iterator_test.cpp(30): error in "test_default_delimeter": test *it == "acv ffg" failed [ != acv ffg] ../libs/test/test/ifstream_line_iterator_test.cpp(36): error in "test_default_delimeter": test *it == " " failed [ != ] ../libs/test/test/ifstream_line_iterator_test.cpp(39): error in "test_default_delimeter": test *it == "1" failed [ != 1] ../libs/test/test/ifstream_line_iterator_test.cpp(51): error in "test_custom_delimeter": test it != utf::ifstream_line_iterator() failed ../libs/test/test/ifstream_line_iterator_test.cpp(53): error in "test_custom_delimeter": test *it == "{ abc d " failed [ != { abc d ] ../libs/test/test/ifstream_line_iterator_test.cpp(56): error in "test_custom_delimeter": test *it == "\n{ d \n dsfg\n" failed [ != ../libs/test/test/ifstream_line_iterator_test.cpp(59): error in "test_custom_delimeter": test *it == "\n" failed [ != ...failed execute-test ..\bin\boost\libs\test\test\ifstream_line_iterator_test.test\vc7.1\debug\ifstream_line_iterator_test.run... ..\libs\test\test\minimal_test.cpp(66): Some error in function: 'int __cdecl test_main(int,char *[])' ...failed RmTemps ..\bin\boost\libs\test\test\minimal_test.test\vc7.1\debug\minimal_test.run... ...failed updating 20 targets... ...skipped 31 targets... ...updated 2839 targets... Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

3 5

BOOST_CHECK_EQUAL: different behaviour on VC 7.1 and Intel
by Stefan Slapeta 21 Jul '04

21 Jul '04

This produces different results on VC 7.1 (fail) and Intel 8 (pass): char *p = "Hi!"; BOOST_CHECK_EQUAL(p, "Hi!"); Stefan

2 2

RE: [boost] Regression results for Intel 8 online
by Aleksey Gurtovoy 21 Jul '04

21 Jul '04

Stefan Slapeta writes: > I've put them here: http://genericprogramming.com/boost Stefan, this is very much appreciated! But these results are ought to be in the overall summary (http://boost.sourceforge.net/regression-logs/developer/summary.html) Could you give a shot to the new regression driver script which, among other things, would take care of it -- http://tinyurl.com/4f2zp? > > Spirit is missing somehow; were the tests not included when > the source was moved to boost CVS? No, that's the current default: Spirit test suite is not included into "boost/status/Jamfile". It appears in Win32 and Lunix tests because both sites path the "Jamfile" locally before running the tests. I think the original reasons for it long lost their merits, though. Same for the MPL. OK, fixed in the CVS. -- Aleksey Gurtovoy MetaCommunications Engineering

2 2

Re: Regression results for Intel 8 online
by Michael Stevens 21 Jul '04

21 Jul '04

On Tuesday 20 July 2004 14:04,Stefan Slapeta <stefan_nospam_(a)slapeta.com> Thanks Stefan for putting these up. With regard to uBLAS there appear to be two problems unique to Intel-8 (Windows). Neither occur on the Linux compiler version! The test2 fails with "unresolved external symbol" std::complex<float>::complex<float>(class std::complex<float> const &) Looks like the compiler has failed to instantiate this template or it is missing from the library! test7 are new tests that combine uBLAS with interval. Results are universally poor on all Windows compiler but in each case for different reasons! In this case the error suggests the windows compiler version is not finding a conversion that exits. Can you post the compiler options for these run. Maybe there are still VC compatibility options set which are introducing compiler bugs! Thanks, Michael

2 1

Multiple link definitions on Darwin tests
by Marshall Clow 21 Jul '04

21 Jul '04

Recently, many of the Darwin tests started failing. A bunch of them were the new serialization tests, and I've been working with Robert Ramey to figure out why and fix them. However, I have come to realize that a lot of the failing tests are not in the serialization library. Before I start debugging this myself, does anyone have any suggestions? For example, _all_ the program options tests are failing, with messages like: <http://boost.sourceforge.net/regression-logs/cs-Darwin-links.html#program_o…> >program_options - cmdline_test - darwin > >Linker output: > >ld: warning table of contents of library: >../bin/boost/libs/test/build/libboost_test_exec_monitor.a/darwin/debug/libboost_test_exec_monitor.a >not sorted slower link editing will result (use the ranlib(1) -s >option) >ld: multiple definitions of symbol >_ZN5boost9unit_test110_GLOBAL__N__ZGVZN5boost9unit_test9ut_detail11xml_printer13print_escapedERSoNS0_13basic_cstringIKcEEE9char_type22first_failed_assertionEv.eh >../bin/boost/libs/test/build/libboost_test_exec_monitor.a/darwin/debug/libboost_test_exec_monitor.a(unit_test_log.o) >definition of absolute >_ZN5boost9unit_test110_GLOBAL__N__ZGVZN5boost9unit_test9ut_detail11xml_printer13print_escapedERSoNS0_13basic_cstringIKcEEE9char_type22first_failed_assertionEv.eh >(value 0x0) >../bin/boost/libs/test/build/libboost_test_exec_monitor.a/darwin/debug/libboost_test_exec_monitor.a(supplied_log_formatters.o) >definition of absolute >_ZN5boost9unit_test110_GLOBAL__N__ZGVZN5boost9unit_test9ut_detail11xml_printer13print_escapedERSoNS0_13basic_cstringIKcEEE9char_type22first_failed_assertionEv.eh >(value 0x0) >ld: multiple definitions of symbol boost::unit_test::(anonymous >namespace)::first_failed_assertion() >../bin/boost/libs/test/build/libboost_test_exec_monitor.a/darwin/debug/libboost_test_exec_monitor.a(unit_test_log.o) >definition of boost::unit_test::(anonymous >namespace)::first_failed_assertion() in section (__TEXT,__text) >../bin/boost/libs/test/build/libboost_test_exec_monitor.a/darwin/debug/libboost_test_exec_monitor.a(supplied_log_formatters.o) >definition of boost::unit_test::(anonymous >namespace)::first_failed_assertion() in section (__TEXT,__text) >ld: warning table of contents of library: >../bin/boost/libs/test/build/libboost_test_exec_monitor.a/darwin/debug/libboost_test_exec_monitor.a >not sorted slower link editing will result (use the ranlib(1) -s >option) > > > export DYLD_LIBRARY_PATH > c++ -g -o >"../bin/boost/libs/program_options/test/cmdline_test.test/darwin/debug/cmdline_test" >"../bin/boost/libs/program_options/test/cmdline_test.test/darwin/debug/cmdline_test.o" >\ > \ > >-L"../bin/boost/libs/program_options/build/libboost_program_options.a/darwin/debug" >-L"../bin/boost/libs/test/build/libboost_test_exec_monitor.a/darwin/debug" >"../bin/boost/libs/program_options/build/libboost_program_options.a/darwin/debug/libboost_program_options-d-1_31.a" >"../bin/boost/libs/test/build/libboost_test_exec_monitor.a/darwin/debug/libboost_test_exec_monitor.a" >"../bin/boost/libs/program_options/build/libboost_program_options.a/darwin/debug/libboost_program_options-d-1_31.a" >"../bin/boost/libs/test/build/libboost_test_exec_monitor.a/darwin/debug/libboost_test_exec_monitor.a" >\ > -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

7 10

Re:Re: [boost] additional boost libraries?
by Robert Ramey 21 Jul '04

21 Jul '04

Vladimir Prus wrote: >> and, just out of curiosity: >> xml/html parsing >None so far. In fact, it seems unlikely that somebody will come along and >implement all the XML stack (DOM, XPath, XML Schema, XSTL, whatever) right >now. One chance would be is somebody boostify some existing XML toolkit -- >but which one? >Another chance is to initially create "tiny XML" library. In fact, both >regression tools and serialization have their own tiny XML parsers and >users aksed about XML support for program_options, so such library might >really be usefull. Note that the serialization library relies upon Spirit 100 % for XML parsing. The spirit package included a very complete example by Dan Nuffer for parsing XML. I copied that (along with a 50 line copyright notice !!!) and slimmed it down to my needs. I had to re-organize a little bit to handle botch char and wchar_t characters. And spirit is kind of abstract so it has a learning curve. Then just when I got "done" (the first time) it was announced that development of spirit was being forked - ARRRRGGGGHHH. Since the spirit developers have seen fit to maintain backward compatibility things have worked well. The code compiles on both spirit 1.6 - the "supported old version" as well Spirit 1.8 - so I'm pleased that the serialization package can be use spirit and still support older compilers without me having to write a yet another half-assed home brew xml parser. I suspect that Spirit is under-appreciated and maybe a little bit ahead of its time. It takes patience, It takes effort, it can sometimes drive you crazy, but using it can make your life better in the long run. I guess its sort of like being in love. Robert Ramey

4 4

Re:[boost] Re: Multiple files utf8_codecvt_facet.cpp
by Robert Ramey 21 Jul '04

21 Jul '04

>Tilman Kuepper >I'm jumping in, because I am interested in Unicode conversion facets... >> is there a reason why both program_options and serialization contain >> very similar files utf8_codecvt_facet.cpp? >I had a look at the serialization library's converter in >utf8_codecvt_facet.cpp >and noticed that utf8_codecvt_facet_wchar_t::do_in() doesn't check for >non-shortest UTF8-sequences. There might also be some issues on >platforms with 16-bit wchar_t (possible overflow). >I suggest using (parts of) the UTF library in the Boost files area to solve >those problems. This could also be another step towards an officially >supported Unicode library... ;-) >http://groups.yahoo.com/group/boost/files/utf/ We really, really need utf-8 facets to be part of boost. I've been pleased with Ron Garcia's that have been included in both the serialization and program options libraries. The only problems we've had is working through the fact that there is a lot of variation in which namespaces different libraries have put things. There were a couple of similar issues regarding function signatures as well. Ron's library also had a nice documentation page. All I had to do was write a test - even that was a hassle and its still not totally satisfactory - it gives bogus warnings. I've thought about Dave's suggestion about each of incorporating source code from a common spot. I was resolved to go along as I'm pleased to off load a stick but peripheral(to me) piece of code. Now I'm rethinking this and am not convinced that it's a good idea. I would like to a) make an "official" spot for it header/lib/ etc. b) move Ron's library into that spot. It's quite serviceable c) entertain "applications" for maintainers. Presumable it would be improved, and/or replaced with time. d) subject the next version to a review. This library has been looked at by various people and although several have offered ideas on how it can be improved - no one has found that it is lacking in the implementation as to what it does. And we need it now. Ron Garcia - Are you out there? Anything to add? Robert Ramey

4 3

RE: [boost] Re: Boost.Test problem
by Rozental, Gennadiy 20 Jul '04

20 Jul '04

> Anyway, the technique I suggested, which we use in Spirit, is > better than your trick of hoisting the names into namespace > std which is a hack that should be avoided if there are other ways. Why is it better? Let's compare: I. Hoisting the names into namespace std - require ifdef/endif + names are fully qualified, that prevent possible ambiguity/invalid function resolution (due to ADL for example) - does not allow to use ADL + located in one place + promote uniformity of access to the symbols in std namespace (particularly in a point on use, so I could see where this symbol came from) II. Use using declaration on function level + doesn't require ifdef/endif + allows ADL usage - unqualified name is a possible source of ambiguity/invalid function resolution - needs to be repeated in all functions that refer symbol - may stand out from the rest of std symbols, potentially leading to confusion/errors My personal preference is fully qualified reference everywhere. And I don't see how other solution is any better. > Regards, > -- > Joel de Guzman Regards, Gennadiy.

2 1