October 2005 - Boost - lists.boost.org

[parameter] BOOST_PARAMETER_KEYWORD does not put identifiers in anonymous namespace.
by Martin Wille 11 Oct '05

11 Oct '05

Hi, the tutorial says: The declaration of the visitor keyword you see here is equivalent to: namespace graphs { namespace tag { struct visitor; } namespace { boost::parameter::keyword<tag::visitor>& visitor = boost::parameter::keyword<tag::visitor>::get(); } } However, BOOST_PARAMETER_KEYWORD(tag, visitor) expands to namespace tag { struct visitor; } ::boost::parameter::keyword<tag::visitor>& visitor = ::boost::parameter::keyword<tag::visitor>::get(); Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com

2 2

Re: [boost] Boost regression notification (2005-10-06 [RC_1_33_0])
by Jonathan Wakely 11 Oct '05

11 Oct '05

(re-sending as the server that hosts this mail account rebooted as I sent the mail and it hasn't shown up in the archives yet ...) Martin Wille wrote: > Arkadiy Vertleyb wrote: > > "Douglas Gregor" <doug.gregor(a)gmail.com> wrote > > > > > >>>Is GCC's debug > >>>mode > >>>a release-critical platform ? > >> > >>No. > > > > > > How can this be? How useful is a feature that can be used in the release > > mode oinly? I think its usefullness is pretty close to zero... > I agree with your questioning, Arkadiy. I completely fail to understand the question. The debug mode cannot be used in "release mode" because it makes the stdlib non-conforming. It's useful for tracking down problems in your code, and as such is immensely useful, but it's not meant for production code in "release mode" What do you mean "a feature that can be used in the release mode only" ? > People will want to use the debug mode. It's probably the best thing > added to recent libstdc++ distributions. Severals bugs in Boost code > were discovered using _GLIBCXX_DEBUG. I'd consider it a big loss not to > be able to use it anymore. I'm not saying "you can't use it anymore" - just that the Boost release shouldn't be held up by debug-mode failures that don't affect any major platforms in their normal configuration. If you're willing, try running the tests with libstdc++ concept-checks enabled as well (#define _GLIBCXX_CONCEPT_CHECKS) and then let me know if you think the release should be held up for those bugs too. Personally I think they're more important than the debug-mode failures, since it's possible to configure GCC so that concept-checks are enabled by default, making parts of Boost unusable. But debug mode is always off by default. jon

5 9

Re: [boost] Boost Digest, Vol 1241, Issue 4
by Jared McIntyre 11 Oct '05

11 Oct '05

> Double check that a is polymorphic - that is, that it has at least one > virtual function. Then get back to us. Yup, the destructors are virtual (and dynamic_cast is working in both directions). However, it works now (see later comment). > nope, its correct. This is a little known quirk of C++ syntax. Your second > version won't compile on the most conforming compilers. Nifty. I swear that didn't compile when I used it on Friday, but now it does. Now that I have changed it to that format, ar.template register_type<derived_one>(), it works. Out of curiosity, what is the difference between calling it that way and calling ar.register_type<derived_one>()? I've not seen that type of format and would be interested in learning more about it. Thanks again, Jared

3 3

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

11 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-10T14:07:23Z 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… 217 failures in 5 libraries: graph (1) iostreams (1) range (3) serialization (207) spirit (5) |graph| graphviz_test: cw-9_4 |iostreams| gzip_test: gcc-4_0-darwin |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_demo_polymorphic: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_demo_polymorphic_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 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_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_diamond_binary_archive: gcc-3_3-darwin test_diamond_binary_archive_dll: gcc-3_3-darwin test_diamond_text_archive: gcc-3_3-darwin test_diamond_text_archive_dll: gcc-3_3-darwin test_diamond_text_warchive: gcc-3_3-darwin test_diamond_text_warchive_dll: gcc-3_3-darwin test_diamond_xml_archive: gcc-3_3-darwin test_diamond_xml_archive_dll: gcc-3_3-darwin test_diamond_xml_warchive: gcc-3_3-darwin test_diamond_xml_warchive_dll: gcc-3_3-darwin 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_map_binary_archive: gcc-3_3-darwin test_map_binary_archive_dll: gcc-3_3-darwin test_map_text_archive: gcc-3_3-darwin test_map_text_archive_dll: gcc-3_3-darwin test_map_text_warchive: gcc-3_3-darwin test_map_text_warchive_dll: gcc-3_3-darwin test_map_xml_archive: gcc-3_3-darwin test_map_xml_archive_dll: gcc-3_3-darwin test_map_xml_warchive: gcc-3_3-darwin test_map_xml_warchive_dll: gcc-3_3-darwin 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_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 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: gcc-3_3-darwin test_set_binary_archive_dll: gcc-3_3-darwin test_set_text_archive: gcc-3_3-darwin test_set_text_archive_dll: gcc-3_3-darwin test_set_text_warchive: gcc-3_3-darwin test_set_text_warchive_dll: gcc-3_3-darwin test_set_xml_archive: gcc-3_3-darwin test_set_xml_archive_dll: gcc-3_3-darwin test_set_xml_warchive: gcc-3_3-darwin test_set_xml_warchive_dll: gcc-3_3-darwin 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: 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 |spirit| bug_000008: gcc-3_4_3-sunos grammar_mt_tests: gcc-3_4_3-sunos owi_mt_tests: gcc-3_4_3-sunos scoped_lock_tests: gcc-3_4_3-sunos scoped_lock_tests_debug: gcc-3_4_3-sunos

5 7

[Serialization] Major regressions on RC_1_33_0
by Douglas Gregor 11 Oct '05

11 Oct '05

The last round of changes to the Serialization library have caused major regressions (205, to be precise) on the RC_1_33_0 branch. If these regressions have not been fixed by Monday morning I will revert these changes automatically. Doug

6 16

BOOST_AUTO_TEST_CASE(tweak)
by troy d. straszheim 11 Oct '05

11 Oct '05

Something minor. The code: BOOST_UNIT_TEST_CASE(something) { ... } expands to struct something_id {}; static void something(); static boost::unit_test::ut_detail::auto_test_unit_registrar something_registrar( boost::unit_test::make_test_case( boost::unit_test::callback0<>(something), boost::unit_test::literal_string( "something", sizeof( "something" ) - 1 ) ), boost::unit_test::ut_detail::auto_tc_exp_fail< something_id>::value ); static void something() { ... } And if you're testing, say, smart_cast of something, you might naturally code (as I just did) BOOST_UNIT_TEST_CASE(smart_cast) { ... } which will contain static void smart_cast() and you'll get a fairly cryptic error, test_smart_cast.cpp:198: error: no matching function for call to 'boost::unit_test::callback0<boost::unit_test::ut_detail::unused>::callback0(<unknown type>)' The docs specify that > To use automatic registration facility you need to define a test case > as a zero arity free function, but instead of usual void tc_name(), > use following statement > > BOOST_AUTO_UNIT_TEST( tc_name ) > > BOOST_TEST_CASE hides all the machinery used to implement automatic > registration. The only requirements are that test case names are > unique within compilation unit and no two test case definition are > located on the same line. Which I didn't see until just now. The context implies that tc_name must be a valid function name, so I guess there's no problem. But it does seem a little redundant to write BOOST_AUTO_TEST_CASE(test_of_smart_cast) { ... } as it's clear you're writing a test. I had assumed the static function were instead named test_case_smart_cast() and hidden in a namespace, something like namespace boost::unit_test::ut_detail::user_tests { struct test_case_smart_cast_id {}; void test_case_smart_cast(); } [etc., etc.] void boost::unit_test::ut_detail::user_tests::test_case_smart_cast() { ... } for added safety against name collisions, as one sees in, e.g., boost::python: # define BOOST_PYTHON_MODULE_INIT(name) \ void init_module_##name(); \ Anyhow, just thinking out loud, not trying to nitpick. I also noticed that the header file auto_unit_test.hpp shows // deprecated #define BOOST_AUTO_UNIT_TEST( f ) BOOST_AUTO_TEST_CASE( f ) so the example in the docs uses the deprecated interface. Just FYI. Thanks for a very handy testing lib, -t

2 1

Re: [boost] [hash] documentation issues (was [TR1 Review] TR1 Formal Review Beginning)
by Alexander Nasonov 11 Oct '05

11 Oct '05

Daniel James wrote: > Alexander Nasonov wrote: >> 2. Adding new has_value may have side effects, for example, (a) hash<T> may >> compile for not customized type T although T doesn't necesarily have >> properly defined equality function; or (b) it may introduce overload >> resolution ambiguities, in worst case, hash<type_from_6_3_3_1> may stop >> working. > > I don't think this is nearly as bad as you think. Any type from TR1 will > only stop working if you declare hash_value in the boost or std > namespace - which you really shouldn't do. You are right. I was a way too pessimistic. > If a type has a hash_value function but no equality then boost::hash > will compile for it - but a hashed container won't, because it will > require the equality function. So the only time will boost::hash will > work is if it's used in another context where equality isn't required. That's not quite right. For example #include <iostream> #include <boost/functional/hash.hpp> struct Base { bool operator==(Base) const { return true; } }; std::size_t hash_value(Base) { return 0; // Base has no state } struct Derived : Base { int dummy; bool operator==(Derived other) const { return dummy == other.dummy; } }; int main() { Derived x; std::cout << boost::hash<Derived>()(x) << '\n'; } -- Alexander Nasonov

5 9

Any interest? complex_utils
by Neal Becker 11 Oct '05

11 Oct '05

I have uploaded a few complex number utilities to boost vault under Math-Numerics/complex-util.tar.gz. Included are 3 kinds of iterator adapters and a test program. Is there interest in further development of this as part of math/numerics library? (I use these myself all the time) If so, there will probably also be a few other small utilities.

3 2

Re: [boost] GUI coordinate units (Was: GUI foundations)
by brangdon＠cix.compulink.co.uk 10 Oct '05

10 Oct '05

In-Reply-To: <dic90t$l4e$1(a)sea.gmane.org> joel(a)boost-consulting.com (Joel de Guzman) wrote (abridged): > Sure they do text. I didn't say they didn't. I just said I didn't find any documentation on it. -- Dave Harris, Nottingham, UK.

2 1

Re: [boost] Interest in dimension/unit-checking library?
by Schrom, Brian T 10 Oct '05

10 Oct '05

I also agree. I find that I was starting to invent some of this in my chart library and a generic, complete solution would be wonderful to use in that context. > <big snip> > >Please to learn that work is still done - IMO we still badly need a good solution to the ubiquitous (but hard) problem of units & dimensions. > >Paul

1 0