- Boost - lists.boost.org

Boost regression notification (2006-11-21 [RC_1_34_0])
by Douglas Gregor 21 Nov '06

21 Nov '06

Boost Regression test failures Report time: 2006-11-20T05:51:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 214 failures in 22 libraries concept_check (60) date_time (2) graph (2) io (1) iostreams (10) iterator (3) lambda (1) math (24) mpl (3) numeric/interval (2) optional (1) parameter (1) python (58) random (1) regex (4) serialization (7) signals (4) spirit (3) statechart (13) test (12) thread (1) utility (1) |concept_check| class_concept_fail_expected: borland-5.6.4 borland-5.8.2 borland-5.8.2 cw-9.4 darwin-4.0.1 gcc-3.2.3_linux gcc-3.3.6 gcc-3.3.6_linux gcc-3.4.4 gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc hp_cxx-71_006_tru64 intel-linux-9.0 intel-vc71-win-9.1 intel-vc8-win-9.1 msvc-6.5 msvc-7.0 msvc-7.1 msvc-7.1 msvc-8.0 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp sun-5.8 concept_check_fail_expected: borland-5.6.4 borland-5.8.2 borland-5.8.2 cw-9.4 darwin-4.0.1 gcc-3.2.3_linux gcc-3.3.6 gcc-3.3.6_linux gcc-3.4.4 gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc hp_cxx-71_006_tru64 intel-linux-9.0 intel-vc71-win-9.1 intel-vc8-win-9.1 msvc-6.5 msvc-7.0 msvc-7.1 msvc-7.1 msvc-8.0 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp sun-5.8 |date_time| testduration: borland-5.8.2 testgenerators_dll: gcc-4.1.0_linux |graph| adj_list_cc: qcc-3.3.5_gpp bfs: intel-linux-9.0 |io| ios_state_test: borland-5.8.2 |iostreams| bzip2_test: msvc-7.1 msvc-8.0 file_descriptor_test: cw-9.4 finite_state_filter_test: cw-9.4 gzip_test: msvc-7.1 msvc-8.0 mapped_file_test: cw-9.4 newline_test: borland-5.8.2 zlib_test: msvc-7.1 msvc-8.0 |iterator| filter_iterator_test: borland-5.8.2 lvalue_concept_fail: borland-5.8.2 msvc-7.1 |lambda| bind_tests_simple: intel-linux-9.0 |math| common_factor_test: borland-5.8.2 cw-9.4 darwin-4.0.1 gcc-3.2.3_linux gcc-3.3.6 gcc-3.3.6_linux gcc-3.4.4 gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc hp_cxx-71_006_tru64 intel-linux-9.0 intel-vc71-win-9.1 intel-vc8-win-9.1 msvc-6.5 msvc-7.0 msvc-7.1 msvc-7.1 msvc-8.0 msvc-8.0 sun-5.8 |mpl| int: borland-5.8.2 integral_c: borland-5.8.2 size_t: borland-5.8.2 |numeric/interval| mul: borland-5.8.2 test_float: borland-5.8.2 |optional| optional_test: borland-5.8.2 |parameter| python_test: msvc-7.1 |python| andreas_beyer: msvc-7.1 args: msvc-7.1 auto_ptr: msvc-7.1 back_reference: msvc-7.1 ben_scott1: msvc-7.1 bienstman1: msvc-7.1 bienstman2: msvc-7.1 bienstman3: msvc-7.1 builtin_converters: msvc-7.1 callbacks: msvc-7.1 const_argument: msvc-7.1 crossmod_exception: msvc-7.1 crossmod_opaque: msvc-7.1 data_members: msvc-7.1 defaults: msvc-7.1 dict: msvc-7.1 docstring: msvc-7.1 enum: msvc-7.1 exception_translator: msvc-7.1 extract: msvc-7.1 implicit: msvc-7.1 injected: msvc-7.1 iterator: msvc-7.1 keywords: msvc-7.1 list: msvc-7.1 long: msvc-7.1 map_indexing_suite: msvc-7.1 minimal: msvc-7.1 multi_arg_constructor: msvc-7.1 nested: msvc-7.1 numpy: msvc-7.1 object: msvc-7.1 opaque: msvc-7.1 operators: msvc-7.1 pearu1: msvc-7.1 pickle1: msvc-7.1 pickle2: msvc-7.1 pickle3: msvc-7.1 pickle4: msvc-7.1 pointer_vector: msvc-7.1 polymorphism: msvc-7.1 polymorphism2: msvc-7.1 polymorphism2_auto_ptr: msvc-7.1 properties: msvc-7.1 raw_ctor: msvc-7.1 return_arg: msvc-7.1 shared_ptr: msvc-7.1 slice: msvc-7.1 staticmethod: msvc-7.1 stl_iterator: msvc-7.1 str: msvc-7.1 test_pointer_adoption: msvc-7.1 try: msvc-7.1 tuple: msvc-7.1 vector_indexing_suite: msvc-7.1 virtual_functions: msvc-7.1 voidptr: msvc-7.1 wrapper_held_type: msvc-7.1 |random| random_test: intel-linux-9.0 |regex| regex_regress: borland-5.8.2 regex_regress_dll: borland-5.8.2 regex_regress_threaded: borland-5.8.2 test_grep: msvc-6.5 |serialization| test_reset_object_address: msvc-7.0 test_reset_object_address_dll: msvc-7.0 test_utf8_codecvt: borland-5.8.2 test_variant_xml_archive: borland-5.8.2 test_variant_xml_archive_dll: borland-5.8.2 test_variant_xml_warchive: borland-5.8.2 test_variant_xml_warchive_dll: borland-5.8.2 |signals| deletion_test: msvc-6.5 ordering_test: msvc-6.5 signal_n_test: msvc-6.5 trackable_test: msvc-6.5 |spirit| switch_tests_single_debug: intel-linux-9.0 symbols_add_null: msvc-7.1 symbols_add_null_debug: msvc-7.1 |statechart| BitMachineExample: cw-9.4 hp_cxx-71_006_tru64 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp CameraExample: cw-9.4 PerformanceExample: cw-9.4 PingPongExample: hp_cxx-71_006_tru64 TransitionTestBoth: qcc-3.3.5_gpp qcc-3.3.5_gpp TransitionTestRelaxed: qcc-3.3.5_gpp qcc-3.3.5_gpp |test| prg_exec_fail1: intel-vc71-win-9.1 intel-vc8-win-9.1 msvc-6.5 msvc-7.0 msvc-7.1 msvc-8.0 prg_exec_fail2: darwin-4.0.1 prg_exec_fail3: borland-5.8.2 cw-9.4 msvc-7.1 test_case_template_test: borland-5.8.2 test_fp_comparisons: cw-9.4 |thread| test_tss_lib: borland-5.8.2 |utility| operators_test: gcc-3.4.5_linux_x86_64

1 0

[Boost-bugs] [ boost-Bugs-1600530 ] Unused argument warnings in serialization code
by SourceForge.net 21 Nov '06

21 Nov '06

Bugs item #1600530, was opened at 2006-11-21 11:42 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1600530&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: date_time Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Caleb Epstein (cepstein) Assigned to: Jeff Garland (az_sw_dude) Summary: Unused argument warnings in serialization code Initial Comment: The various "version" and "file_version" arguments to the date_time serialization methods are unused, leading to compiler warnings from gcc. Patch is attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1600530&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

mistaken uses of <iostream>
by Howard Hinnant 21 Nov '06

21 Nov '06

<iostream> is the only C++ header that extracts a cost simply by including it (in typical implementations). The usual implementation is for it to include a static object of type std::ios_base::Init which is responsible for initializing the 8 terminal streams (cin, cout, cerr, clog, wcin, wcout, wcerr, wclog). I've always thought it good programming practice to avoid including <iostream> if the translation unit didn't actually need one of these 8 terminal streams. For example if I needed to just get to istream and ostream to write my own I/O I would include <istream> and <ostream> but not <iostream> (the naming is very unfortunate). It has recently come to my attention that I could be overly sensitive to this issue and making a fuss about nothing. So I'm writing here for a reality check. Do boost programmers consider the use of <iostream> as a short cut to get to non-terminal-streams I/O a reasonable technique? Or do boost programmers feel that use of <iostream> should be reserved only when using one or more of cin, cout, cerr, clog, wcin, wcout, wcerr, wclog? I did a brief survey of boost 1.33.1 and found many "relaxed" uses of <iostream> under the boost/ directory (i.e. non test-case code). So in practice it does appear that using <iostream> as a shortcut is considered acceptable practice. However I wanted to highlight the point just in case people do view this as a bug that has simply snuck in under the radar to date. -Howard

10 13

[Boost-bugs] [ boost-Patches-1551992 ] [shared_ptr] support for STLport 5's no-iostreams mode
by SourceForge.net 21 Nov '06

21 Nov '06

Patches item #1551992, was opened at 2006-09-04 06:41 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1551992&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: smart_ptr Group: None >Status: Closed Resolution: Accepted Priority: 5 Private: No Submitted By: Michael Fink (vividos) Assigned to: Peter Dimov (pdimov) Summary: [shared_ptr] support for STLport 5's no-iostreams mode Initial Comment: In STLport there is a mode called no-iostreams mode. When the define _STLP_NO_IOSTREAMS is used, nothing of the iostreams-part of the Standard C++ Library can be used, and including the headers fails with an error. The advantage of this mode is that the user doesn't have to link against a built library, all STLport code is inline. Unfortunately the shared_ptr cannot be used in this mode, since an operator<< is defined in shared_ptr.hpp. This patch ifdef's out this operator when _STLP_NO_IOSTREAMS symbol is defined (and it does the same with intrusive_ptr.hpp). The patch is against the 1.34 branch of CVS. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2006-11-20 19:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Peter Dimov (pdimov) Date: 2006-11-06 09:27 Message: Logged In: YES user_id=305912 Applied to 1.34 and HEAD. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1551992&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[fusion] boost::array problem under msvc-8.0
by Michael Marcin 21 Nov '06

21 Nov '06

Hi, I've been toying around with the idea of using fusion in my geometry library (at least that seems to be the terminology in use around here). I started reading the documentation and I ran into a problem with the firs thing I tried to do. #include <boost/array.hpp> #include <boost/fusion/iterator.hpp> #include <boost/fusion/sequence.hpp> #include <iostream> int main() { namespace fusion = boost::fusion; boost::array<float,3> position = { {0.f, 1.f, 2.f} }; std::cout << deref( fusion::begin(position) ) << std::endl; return 0; } fails to compile with: ------------------------------------------------------ main.cpp c:\code\boost-head\boost\boost\fusion\sequence\adapted\array\array_iterator.hpp(62) : error C2676: binary '[' : 'boost::array<T,N>' does not define this operator or a conversion to a type acceptable to the predefined operator with [ T=float, N=3 ] c:\code\boost-head\boost\boost\fusion\sequence\adapted\array\array_iterator.hpp(61) : while compiling class template member function 'float &boost::fusion::array_iterator<Array,Pos>::deref<Iterator>::call(const Iterator &)' with [ Array=boost::array<float,3>, Pos=0, Iterator=boost::fusion::array_iterator<boost::array<float,3>,0> ] c:\code\boost-head\boost\boost\fusion\iterator\deref.hpp(35) : see reference to class template instantiation 'boost::fusion::array_iterator<Array,Pos>::deref<Iterator>' being compiled with [ Array=boost::array<float,3>, Pos=0, Iterator=boost::fusion::array_iterator<boost::array<float,3>,0> ] c:\code\boost-head\boost\boost\fusion\iterator\deref.hpp(54) : see reference to class template instantiation 'boost::fusion::extension::deref_impl<boost::fusion::iterator_facade_tag>::apply<Iterator>' being compiled with [ Iterator=boost::fusion::array_iterator<boost::array<float,3>,0> ] c:\code\geometry\source\main.cpp(95) : see reference to class template instantiation 'boost::fusion::result_of::deref<Iterator>' being compiled with [ Iterator=boost::fusion::array_iterator<boost::array<float,3>,0> ] ------------------------------------------------------ changing deref::call from: return it.array[Iterator::index::value]; to: return it.array.at( Iterator::index::value ); causes it to compile so I'm thinking it is a compiler bug that needs to be worked around.

2 2

[fusion] tag_of example
by Michael Marcin 20 Nov '06

20 Nov '06

The fusion tag_of example on this page (from latest CVS HEAD) doesn't seem to make any sense and has at least one syntax error. ./boost/libs/fusion/doc/html/fusion/support/tag_of.html - Michael Marcin

2 1

Dean Michael Berris wants to share sites with you...
by mikhailberis＠gmail.com 20 Nov '06

20 Nov '06

Dean Michael Berris (mikhailberis(a)gmail.com) has invited you to StumbleUpon! You can see my other favorites here: http://mikhailberis.stumbleupon.com Thanks, mikhailberis --- StumbleUpon lets you discover great sites with a single click. Give it a try at: http://www.stumbleupon.com/join.php?friend=152005&emailcode=koezt4bir3pg6dbb

1 0

[Mat Marcus] [Paul Moore] [Vesa Karvonen] Email address wanted
by Andreas Huber 20 Nov '06

20 Nov '06

While correcting license & copyright issues in the people pages I've come across several pages where I don't know how to contact the copyright owners. Does anybody know how to contact Mat Marcus, Paul Moore or Vesa Karvonen by email? Thanks, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.

3 2

wiki has been spammed
by Jan Stetka 20 Nov '06

20 Nov '06

The wiki has been spammed. Its just the front page. It would be good to make it editable only by people who have asked for access to it. The proper wiki front page is still available in previous revisions, but can't be reverted. Thanks

3 3

Borland patch for MPL tests
by AlisdairM 20 Nov '06

20 Nov '06

A patch for the failing Borland tests for the JustSoftwareSolutions test runner follows. The patch is for the test, but I believe it is appropriate in this case: The problem only occurs when function inlining is available The problem comes from obscure use of is_same template as a function argument The problem only occurs if this is the first/only use of that is_same specialization There are additional factors required to trigger problem, such as use of iostream vs C-based io The problem only occurs when ALL of the above are true, and is essentially a consquence of the test being stripped down to test nothing but this specific test case. Most user programs are not stripped down test cases, and will never hit the problem. THe patch simply takes a typedef to the tested types, and then tests that, so the test is not materially changed. -- AlisdairM cvs diff -u -wb -- test\integral_wrapper_test.hpp (in directory E:\sourceforge\rc_1_34_0\boost\libs\mpl\) Index: test/integral_wrapper_test.hpp =================================================================== RCS file: /cvsroot/boost/boost/libs/mpl/test/integral_wrapper_test.hpp,v retrieving revision 1.4 diff -u -w -b -r1.4 integral_wrapper_test.hpp --- test/integral_wrapper_test.hpp 20 Feb 2006 15:45:07 -0000 1.4 +++ test/integral_wrapper_test.hpp 19 Nov 2006 08:58:14 -0000 @@ -28,6 +28,20 @@ /**/ #endif +#if BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT( 0x582) ) +#define INTEGRAL_WRAPPER_TEST(unused1, i, T) \ + { \ + typedef WRAPPER(T,i) borland_tested_type; \ + { typedef is_same< borland_tested_type::value_type, T > borland_test_type; \ + MPL_ASSERT(( borland_test_type )); } \ + { MPL_ASSERT(( is_same< borland_tested_type::type, WRAPPER(T,i) > )); } \ + { MPL_ASSERT(( is_same< next< borland_tested_type >::type, WRAPPER(T,i+1) > )); } \ + { MPL_ASSERT(( is_same< prior< borland_tested_type >::type, WRAPPER(T,i-1) > )); } \ + { MPL_ASSERT_RELATION( (borland_tested_type::value), ==, i ); } \ + INTEGRAL_WRAPPER_RUNTIME_TEST(i, T) \ + } \ +/**/ +#else #define INTEGRAL_WRAPPER_TEST(unused1, i, T) \ { MPL_ASSERT(( is_same< WRAPPER(T,i)::value_type, T > )); } \ { MPL_ASSERT(( is_same< WRAPPER(T,i)::type, WRAPPER(T,i) > )); } \ @@ -36,3 +50,5 @@ { MPL_ASSERT_RELATION( (WRAPPER(T,i)::value), ==, i ); } \ INTEGRAL_WRAPPER_RUNTIME_TEST(i, T) \ /**/ +#endif +

2 1