October 2007 - Boost - lists.boost.org

[xpressive] HP-UX_ia64_aCC problem ... care to help?
by Eric Niebler 17 Oct '07

17 Oct '07

Two of xpressive's tests are crashing on the HP-UX_ia64_aCC platform. Is there anybody with access to this platform that would like to help me track it down? Just run xpressive's "test_actions" test and send me a backtrace of the crash. Whoever helps gets a gold star. :-) -- Eric Niebler Boost Consulting www.boost-consulting.com

2 5

force threading
by Gennadiy Rozental 17 Oct '07

17 Oct '07

How do I force <threading>single for cw toolset?

1 0

[boos][Trac] Anybody tried the code review plugin?
by John Femiani 16 Oct '07

16 Oct '07

I noticed that there is a code review plug-in for Trac. Since boost seems to be using Trac now, does anybody else think that this could be nice to have as part of the boost process? I don't have experience using the plugin but it seems nice to me. -- John

2 1

Future of Boost.Thread, date-time, and C++0x
by Jeff Garland 16 Oct '07

16 Oct '07

At the Kona meeting (just finished) the standard committee made very significant progress on threading for C++0x -- voting in a proposal written by Howard H, Beman, Anthony Williams, myself, and others -- subject to wording changes to be made by a small drafting committee. Basically we were in agreement on semantics, but even after several late night drafting sessions people weren't happy with the standardeze. While much of the proposal is based on Boost.thread it has some serious departures in the way mutexes and guard interfaces work, it's use of date-time types for clock/timing interfaces and such. At this point I feel it would be very important to have a reference implementation widely available to Boosters and others to play with so that any issues are shaken out while there's still time tweak things. Howard has been maintaining a reference implementation, but this is a call out to the broader thread development team (not sure who all that is now besides Anthony) to consider how we might formalize this into Boost.threads. Thoughts? Jeff

8 15

[mipspro] shared libraries issue
by Vladimir Prus 16 Oct '07

16 Oct '07

Per: http://tinyurl.com/yuh7m4 Boost.Python fails to link on MIPSPRO toolset. The errors suggest that the linker tries to create executable, not a shared library, and in fact, I don't see any linker flag potentially causing shared library to be created in mipspro.jam:link.dll Any ideas? - Volodya

1 0

Rapid turnaround testing
by Beman Dawes 16 Oct '07

16 Oct '07

As an experiment, I've got a script that is checking svn every 15 minutes, and if there is a change, running the regression tests and uploading results to a web site. For current VC++ results, see http://mysite.verizon.net/beman/win32-trunk-results.html On these runs the reporting is set to show a row only if the results are something other than a simple "pass" without link. For slightly outdated Linux results, see http://mysite.verizon.net/beman/ubuntu-trunk-results.html Here the results show all tests, regardless of result. The idea is to supplement the regular regression tests at http://beta.boost.org/development/tests/trunk/developer/serialization.html with rapid turnaround tests on a few major platforms, aimed at giving developers quick response as they try to fix bugs affecting platforms they don't have access to. At the current level failures, the Win32 tests are turning around in 11 minutes while the Linux tests turn in 4 minutes. Thus worst case developers can see test results in 26 minutes! It seems to me this might be helpful to developers. Opinions? Presumably in regular use the upload would go to a centralized site. Or maybe decentralization is useful for reliability; a boost web page could contain links. Opinions on that? Which reporting do you prefer? My preference is just to show the tests with something to report. --Beman

6 9

[utility] value_init warning
by Gennadiy Rozental 16 Oct '07

16 Oct '07

Hi, I am buiulding trunk vertion of Boost.Test with msvc 8.0 and see following warning: ..\..\..\boost/utility/value_init.hpp(73) : warning C4345: behavior change: an object of POD type constructed with an initializer of the form () will be default-initialized ..\..\..\boost/utility/value_init.hpp(70) : while compiling class template member function 'boost::vinit_detail::non_const_T_base<T>::non_const_T_base(void)' with [ T=arg ] ..\..\..\boost/utility/value_init.hpp(139) : see reference to class template instantiation 'boost::vinit_detail::non_const_T_base<T>' being compiled with [ T=arg ] ..\..\..\boost/mpl/for_each.hpp(72) : see reference to class template instantiation 'boost::value_initialized<T>' being compiled with [ T=arg ] ..\..\..\boost/mpl/for_each.hpp(97) : see reference to function template instantiation 'void boost::mpl::aux::for_each_impl<false>::execute<first,last,TransformOp,F>(Iterator *,LastIterator *,TransformFunc *,F)' being compiled with [ TransformOp=boost::mpl::make_identity<boost::mpl::_>, F=boost::unit_test::ut_detail::generate_test_case_4_type<boost::unit_test::ut_detail::template_test_case_gen<free_test_function,numbers>,free_test_function>, Iterator=first, LastIterator=last, TransformFunc=boost::mpl::make_identity<boost::mpl::_> ] ..\..\..\boost/test/test_case_template.hpp(123) : see reference to function template instantiation 'void boost::mpl::for_each<TestTypesList,boost::mpl::make_identity<T>,boost::unit_test::ut_detail::generate_test_case_4_type<Generator,TestCaseTemplate>>(F,Sequence *,TransformOp *)' being compiled with [ TestTypesList=numbers, T=boost::mpl::_, Generator=boost::unit_test::ut_detail::template_test_case_gen<free_test_function,numbers>, TestCaseTemplate=free_test_function, F=boost::unit_test::ut_detail::generate_test_case_4_type<boost::unit_test::ut_detail::template_test_case_gen<free_test_function,numbers>,free_test_function>, Sequence=numbers, TransformOp=boost::mpl::make_identity<boost::mpl::_> ] ..\..\..\boost/test/test_case_template.hpp(118) : while compiling class template member function 'boost::unit_test::ut_detail::template_test_case_gen<TestCaseTemplate,TestTypesList>::template_test_case_gen(boost::unit_test::const_string)' with [ TestCaseTemplate=free_test_function, TestTypesList=numbers ] test_case_template_example.cpp(27) : see reference to class template instantiation 'boost::unit_test::ut_detail::template_test_case_gen<TestCaseTemplate,TestTypesList>' being compiled with [ TestCaseTemplate=free_test_function, TestTypesList=numbers ] Can we do something about it? Gennadiy

3 4

[Exception] Do we really need to register?
by Josh Napoli 16 Oct '07

16 Oct '07

I like the append capability of the Exception library I wrote an exception type that packed passed values into a "cons-list" (from the tuple library), and used stream-inserter syntax. The concise syntax has proven to be effective at preventing laziness with error cases. Support for asynchronous exception handling is also very important, but is missing from Exception. Can exception::pimpl remember the user exception type (CRTP), for the sake of clone/raise? The need to preregister tag types is slightly annoying. The need to specify the data-type with the tag is especially annoying. Why not use accompanying text as a key to retrieve values? For example, I would rather write this: class my_exception : public exception<my_exception> {}; void main() { try { int value=5; throw exception() << "Something went wrong. value=" << value; } catch(my_exception& e) { int value=e.get<int>("value="); //search for a field preceded by "value=" cout << value; } } You wouldn't even need to give the key text if you expect the field type to be unique in the exception. The internal map seems awkward, particularly because it discards the order in which attributes are added. -Joshua Napoli

2 2

[soc] Boost.extension/reflection project advances
by Mariano Gabriel Consoni 16 Oct '07

16 Oct '07

Hi Community...! As some of you may know, I'm working on a SoC project called "Boost.extensions and reflection". This mail is just to keep you informed about the project advances. At this time, we have very good news. The library is now near completion, and we expect submitting it for revision in the next days. We've been worked the last two weeks in the following tasks: - Code style: continued improving the code style according Boost guidelines. - Build: improved the Jamfiles to work well in more platforms. - Boost::function: migrated some code to (optionally) use boost::function. - Benchmarks: made new benchmarks to test the new integrations. - Performance analysis: documented the results of the benchmarks. - Preprocessor: replaced a lot of boiler-plate code with (optional) boost::preprocessor macros. - Dependencies flags: documented the optional dependencies and how to enable them. As I have finished all the tasks planned in my proposal (and a lot more :) ) I will advance to Reflection part and Jeremy (Pack, original author) will finish some remaining tasks of Extension. Bye! -- Mariano

4 6

[test] BOOST_AUTO_TEST for gcc broken on trunk
by Jürgen Hunold 16 Oct '07

16 Oct '07

Hi ! The latest changes to Boost.Test broke gcc (at least for me) running the Boost.Test testsuite _all_ tests using BOOST_AUTO_TEST fail with -- snip -- terminate called after throwing an instance of '__gnu_cxx::recursive_init_error' what(): std::exception --snap-- I've attached the output of one test run and the corresponding stack trace. I've traced this down to unit_test_suite_impl.hpp, line 287. This is: static auto_tc_exp_fail*& instance() { ->> static auto_tc_exp_fail inst; static auto_tc_exp_fail* inst_ptr = &inst; return inst_ptr; } It seems that gcc does something different than msvc... Ah, yes, gcc -v yields: Using built-in specs. Target: x86_64-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix=-4.1 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux Thread model: posix gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) Any ideas on how to solve this ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

3 2