September 2005 - Boost - lists.boost.org

[Test] passed assertion count off by 1
by Kim Barrett 24 Sep '05

24 Sep '05

Using Boost.Test from the boost 1.33 release, The reported number of passed assertions for each test case is one greater than the actual number of assertions performed by the test case. For example, the most trivial of auto-unit-test programs, attached below, reports 1 assertion out of 1 passed. I see no test assertions here. ---------- #define BOOST_AUTO_TEST_MAIN #include <boost/test/unit_test.hpp> #include <boost/test/auto_unit_test.hpp> BOOST_AUTO_UNIT_TEST(test_no_assertions) { }

2 1

BOOST_ASSERT and __assume
by Marcin Kalicinski 24 Sep '05

24 Sep '05

Hi Everybody, I see there are mixed opinions on use of __assume in BOOST_ASSERT. The chief concern is there are people using BOOST_ASSERT in "uncommon" (but still valid) ways, such as: - to show dialog box, but only in debug mode - using assert handler to throw during unit testing - possibly more These types of usage would be prohibited if we introduced __assume into BOOST_ASSERT, so basically this is a no-no from stability point of view (nobody wants his code broken). Btw. the second way can be dealt with with disabling __assume if assertion handler is defined. On the other hand some people (including me) consider __assume to be nice, helping optimization and suppressing annoying warnings. I see 3 options: 1. BOOST_ASSUME =============================================== Put __assume in BOOST_ASSUME and leave BOOST_ASSERT unmodified. Pros: - does not disturb existing code in any way Cons: - no existing code uses it, i.e. all existing libraries would have to be modified to take advantage of it; this will probably never happen so most of the code will not benefit - obscure: most of the people would be confused about it when seeing it for the first time 2. BOOST_ASSERT + define to enable assume (default: on) =============================================== Pros: - does enable assume on all the boost code, some user programs get somewhat smaller and faster without any intervention from the programmer Cons: - breaks user code which uses BOOST_ASSERT in "uncommon" way. Would require a change in docs that executing BOOST_ASSERT(false) is undefined behavior (i.e. different than std::assert) BOOST_ASSERT + define to enable assume (default: off) =============================================== Pros: - does enable assume on all the boost code, some user programs get smaller and faster with a simple -D"BOOST_ASSERT_USE_ASSUME" on command line. Cons: - only small number of users will know about that #define, so probably most of the code will not benefit. What do you think? Marcin

4 3

Patch to boost/detail/interlocked.hpp
by Anthony Williams 23 Sep '05

23 Sep '05

I am trying to change my call_once implementation for boost.thread, so it doesn't require windows.h to be included. In doing so, I tried to use boost/detail/interlocked.hpp, and discovered that it doesn't work on gcc-mingw-4.0.1, since the imported functions are declared in boost::detail namespace, and the macros don't qualify the names. Attached is a patch for the file that changes the macros to refer to the imported functions by fully qualified names. Please can someone check and commit this for me. Anthony -- Anthony Williams Software Developer

2 4

Re: [boost] [scope_guard] New revision available + naming consideration
by Jason Stewart 23 Sep '05

23 Sep '05

I sent this earlier but it never showed up on the list. > > By the way, that might work well for smart > > pointers; why don't shared_ptr and friends use this idiom? > >Maybe because it allows more than a literal zero? I personally like the guard/dismiss names, they are reminiscent of commands you would give a real guard. However, maybe using the shared_ptr semantics would work. I.e. if you can create a guard that is "uninitialized" and then reset it later to an active guard. { scope_guard g; if (some condition) { g = scope_guard(my_undo_function); // do something here } if (some other condition) { // we changed our mind, dismiss it. g = scope_guard; // or ... // g.dismiss(); // g.reset(); // like shared_ptr } } It seems to me that is as easy to read as having an explicit "guard" or "activate" command is. I confess though that I didn't follow the early discussion closely so I apologize is this has been discussed already. Jason Stewart

4 6

[Boost-bugs] [ boost-Support Requests-1301634 ] Serialization lib missing
by SourceForge.net 23 Sep '05

23 Sep '05

Support Requests item #1301634, was opened at 2005-09-23 10:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1301634&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: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Serialization lib missing Initial Comment: my email is jla2w(a)yahoo.com I am building the boost library and am specifically interested in serialization. When I follow the steps, I can't get the bjam.exe to recognize the version of spirit that would enable xml serialization. I did the following set SPIRIT_ROOT=C:/Documents and Settings/Luke/Desktop/spirit-1.6.3/boost as well as a couple other variants (not including the last boost) because it isn't clear to me which directory depth it needs to be..anyway, I get errors building the serialization libs (all others build correctly) with messages that choke on the xml files and then many that say that fatal error: Compiler not supported, check config.hpp this is presumably related to spirit env variable not being recognized. The other errors say that the libs were skipped for lack of other libs. One example is ...libboost_serialization-vc7-sgd.lib skipped for lack of libboost_serialization-vc7-sgd-1_33.lib Any ideas? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1301634&group_… ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost regression notification (2005-09-23 [RC_1_33_0])
by Douglas Gregor 23 Sep '05

23 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-23T14:27:13Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. utility/enable_if Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 75 failures in 7 libraries: foreach (1) graph (5) random (1) range (3) serialization (56) thread (8) utility/enable_if (1) |foreach| rvalue_const: vc-7_1 |graph| betweenness_centrality_test: gcc-3.4.4-linux dag_longest_paths: gcc-3.4.4-linux dijkstra_cc: gcc-3.4.4-linux dijkstra_heap_performance: gcc-3.4.4-linux relaxed_heap_test: gcc-3.4.4-linux |random| random_test: gcc-3.3.6-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_contained_class_xml_archive: gcc-3.2.3-linux test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 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_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 |thread| test_barrier_lib: intel-9.0-linux test_condition_lib: intel-9.0-linux test_mutex_lib: intel-9.0-linux test_once_lib: intel-9.0-linux test_read_write_mutex_lib: intel-9.0-linux test_thread_lib: intel-9.0-linux test_tss_lib: intel-9.0-linux test_xtime_lib: intel-9.0-linux |utility/enable_if| no_disambiguation: gcc-3.2.3-linux

1 0

Boost regression notification (2005-09-23 [HEAD])
by Douglas Gregor 23 Sep '05

23 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-23T05:00:15Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. utility/enable_if typeof Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 189 failures in 15 libraries: concept_check (14) filesystem (8) foreach (7) graph (4) math (3) mpl (7) parameter (17) python (1) regex (1) serialization (40) spirit (2) thread (24) typeof (41) utility/enable_if (16) wave (4) |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 vc-7_1 |filesystem| convenience_test: msvc default_name_check_test: msvc fstream_test: msvc large_file_support_test: msvc operations_test: msvc operations_test_dll: msvc path_test: msvc path_test_dll: msvc |foreach| user_defined: cw-8_3 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-6_5-stlport vc-7_0 |graph| graphviz_test: vc-7_1 vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |math| octonion_test: gcc-4_0-darwin quaternion_test: gcc-4_0-darwin special_functions_test: gcc-4_0-darwin |mpl| back: vc-7_1 count_if: vc-7_1 deque: vc-7_1 distance: vc-7_1 erase_range: vc-7_1 size_t: gcc-4_0-darwin gcc-4_0-darwin |parameter| basics: borland-5_6_4 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: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| data_members: msvc |regex| static_mutex_test: msvc |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin 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: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin 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| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_barrier: msvc test_barrier_lib: intel-9.0-linux msvc test_condition: msvc test_condition_lib: intel-9.0-linux msvc test_mutex: msvc test_mutex_lib: intel-9.0-linux msvc test_once: msvc test_once_lib: intel-9.0-linux msvc test_read_write_mutex: msvc test_read_write_mutex_lib: intel-9.0-linux msvc test_thread: msvc test_thread_lib: intel-9.0-linux msvc test_tss: msvc test_tss_lib: intel-9.0-linux msvc test_xtime: msvc test_xtime_lib: intel-9.0-linux msvc |typeof| data_member_emulation: cw-9_4 data_member_native: intel-win32-9_0 intel-win32-9_0 function_emulation: cw-9_4 function_native: intel-win32-9_0 intel-win32-9_0 msvc function_ptr_emulation: cw-9_4 function_ptr_native: intel-win32-9_0 intel-win32-9_0 function_ref_emulation: cw-9_4 function_ref_native: intel-win32-9_0 intel-win32-9_0 lvalue_emulation: cw-9_4 lvalue_native: intel-win32-9_0 intel-win32-9_0 msvc member_function_emulation: cw-9_4 member_function_native: intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_emulation: cw-9_4 template_int_native: intel-win32-9_0 intel-win32-9_0 template_tpl_emulation: cw-9_4 template_tpl_native: intel-win32-9_0 intel-win32-9_0 msvc template_type_emulation: cw-9_4 template_type_native: intel-win32-9_0 intel-win32-9_0 type_emulation: cw-8_3 cw-9_4 cw-9_4 type_native: intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 |utility/enable_if| constructors: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux dummy_arg_disambiguation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux lazy: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux lazy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux member_templates: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux namespace_disambiguation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux no_disambiguation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux partial_specializations: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: gcc-3.3.6-linux intel-9.0-linux

1 0

Boost regression notification (2005-09-22 [HEAD])
by Douglas Gregor 23 Sep '05

23 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-22T05:00:09Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. utility/enable_if typeof Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 184 failures in 15 libraries: concept_check (14) filesystem (8) foreach (7) graph (4) math (3) mpl (2) parameter (17) python (1) regex (1) serialization (40) spirit (2) thread (24) typeof (41) utility/enable_if (16) wave (4) |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 vc-7_1 |filesystem| convenience_test: msvc default_name_check_test: msvc fstream_test: msvc large_file_support_test: msvc operations_test: msvc operations_test_dll: msvc path_test: msvc path_test_dll: msvc |foreach| user_defined: cw-8_3 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-6_5-stlport vc-7_0 |graph| graphviz_test: vc-7_1 vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |math| octonion_test: gcc-4_0-darwin quaternion_test: gcc-4_0-darwin special_functions_test: gcc-4_0-darwin |mpl| size_t: gcc-4_0-darwin gcc-4_0-darwin |parameter| basics: borland-5_6_4 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: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| data_members: msvc |regex| static_mutex_test: msvc |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin 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: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin 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| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_barrier: msvc test_barrier_lib: intel-9.0-linux msvc test_condition: msvc test_condition_lib: intel-9.0-linux msvc test_mutex: msvc test_mutex_lib: intel-9.0-linux msvc test_once: msvc test_once_lib: intel-9.0-linux msvc test_read_write_mutex: msvc test_read_write_mutex_lib: intel-9.0-linux msvc test_thread: msvc test_thread_lib: intel-9.0-linux msvc test_tss: msvc test_tss_lib: intel-9.0-linux msvc test_xtime: msvc test_xtime_lib: intel-9.0-linux msvc |typeof| data_member_emulation: cw-9_4 data_member_native: intel-win32-9_0 intel-win32-9_0 function_emulation: cw-9_4 function_native: intel-win32-9_0 intel-win32-9_0 msvc function_ptr_emulation: cw-9_4 function_ptr_native: intel-win32-9_0 intel-win32-9_0 function_ref_emulation: cw-9_4 function_ref_native: intel-win32-9_0 intel-win32-9_0 lvalue_emulation: cw-9_4 lvalue_native: intel-win32-9_0 intel-win32-9_0 msvc member_function_emulation: cw-9_4 member_function_native: intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_emulation: cw-9_4 template_int_native: intel-win32-9_0 intel-win32-9_0 template_tpl_emulation: cw-9_4 template_tpl_native: intel-win32-9_0 intel-win32-9_0 msvc template_type_emulation: cw-9_4 template_type_native: intel-win32-9_0 intel-win32-9_0 type_emulation: cw-8_3 cw-9_4 cw-9_4 type_native: intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 |utility/enable_if| constructors: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux dummy_arg_disambiguation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux lazy: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux lazy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux member_templates: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux namespace_disambiguation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux no_disambiguation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux partial_specializations: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: gcc-3.3.6-linux intel-9.0-linux

4 3

Re: [boost] [scope_guard] New revisionavailable + namingconsideration
by Greer, Joe 23 Sep '05

23 Sep '05

> Rob Stewart wrote: > > "Secure" is another choice. > Secure brings up images of encryption to me. Activate/Deactivate pair well as do a simple on/off as was also mentioned. joe

1 0

Re: [boost] Errors compiling multi_index hashed.cpp
by Joaquín Mª López Muñoz 23 Sep '05

23 Sep '05

David Crayford ha escrito: > Thanks Joaquin, actually the z/OS release is 6. I t= ried changing > __IBMCPP__ to 600 but it screwed the compile. OK. Well, the following is a slightly more convoluted way to check whether your compiler is able to cope with Boost, more or less: 1. Globally search "__IBMCPP__" in the codebase (about 100 occurrences) and replace it with, say, BOOST_IBMCPP. This task should be simple if you're a Unix man. 2. Compile your test code with a compiler switch defining the macro BOOST_IBMCPP to 600. I think in your case the compiler switch is -DBOOST_IBMCPP=600 3. Shake and serve. Please report your results back. Thank you! > I'm new to this list, how do I contact J= ohn Maddock? He's a regular on this list. If you post a message with a more focused subject line surely he'll delve in. > BTW, I'm sorry if my mails are mang= led, it seems to be a problem > with the lotus notes browser client. You can use web-based gmane service for posting to the list: http://news.gmane.org/gmane.comp.lib.boost.devel Good luck, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 5