February 2007 - Boost - lists.boost.org

[timer]Behavior under MS Windows and documentation
by Yuriy Koblents-Mishke 02 Feb '07

02 Feb '07

Dear Mr. Dawes: First of all, I would like to thank you for the small, but very convenient class. I used it for timing my CPU-intensive codes. However, while using it on Windows machines, I encountered a problem not reflected in documentation: == Summary: == Boost Timer measures a conceptually different timing under Windows than under other operation systems. It is proposed to describe the difference in documentation. For modern versions of Windows the problem can be fixed easily, but with Windows 95/98/ME it is not so. == Description == Under most of operation systems, Boost Timer measures the CPU time consumed by a program. The timing does not include CPU cycles used by other programs running on the same computer, nor the time when the program is waiting for I/O. Under Windows, Boost Timer measures instead the whole wall-clock time elapsed. If other resource-hogging programs like Norton Antivirus, Norton Speed Disk defragmentor, or Skype are running simultaneously with a timed program, the timer will reflect it. If you are timing five copies of the same CPU-bound program, Boost Timer reports that the program became five times slower. If the timed program is waiting for an user input, the timer reports how long coffee break the user took. All of this makes Boost Timer, well, not very suitable for timing of CPU bound codes running under Windows. Even for a rough timing. == The reason == The underlying problem is in std::clock(). Under Windows, the function does not measure the amount of CPU time used by a process. It measures instead the "wall clock" time elapsed since the program started: http://msdn2.microsoft.com/en-us/library/4e2ess30(VS.80).aspx see also discussion here: http://www.cygwin.com/ml/cygwin/2004-07/msg00164.html http://www.cygwin.com/ml/cygwin/2004-07/msg00175.html The Microsoft documentation shows that it is true for all current and recent desktop versions of Windows, starting from year 1995. To my recollection, it was true for MS DOS as well. Hardly an ANSI behavior, but it is so. == Possible solutions == 1. Taking in account how many computers are running Windows, I would suggest to describe the difference in Boost Timer documentation. Currently the documentation discusses a relatively minor problem with low resolution of Boost Timer under Windows, but does not mention the much bigger issue. 2. It is more debatable is if it makes sense to fix the class. 2.1. Boost Timer was around for so many years already, that it probably makes sense to retain its old behavior for compatibility - like Microsoft did with clock() for compatibility with DOS. Personally, I would implement the fixes as a separate class cpu_timer. 2.2. As it was discussed in the Rationale section of documentation, different versions of Windows would require different fixes: On all modern desktop and server versions of MS Windows, starting from NT ver. 3.51 and including all versions of Windows 2000, Windows XP, Windows Server 2003, and Windows Vista the right behavior can be implemented using function GetThreadTimes described in Microsoft documentation: http://msdn2.microsoft.com/en-us/library/ms683237.aspx Windows CE, strating from versions 3.0 or even 2.12, also supports this function, but vendors can remove it from vendor-specific builds: http://msdn2.microsoft.com/en-us/library/ms908464.aspx For Intel Pentium 4 processors running in hyper-threading mode the solution will give distorted result, but it is probably unavoidable. See an useful discussion on the Microsoft forum: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=990282&SiteID=1 The solution is completely incompatible with Windows 95 / 98 / ME, because the OS do not support the GetThreadTimes function. Is there is still a need to support these quaint versions of Windows in the year 2007? == Additional question == You mentioned in the documentation a rejected Win32 implementation submitted by John Maddock. Where can I find it? I would like to compare it to my timing codes for Windows. Sincerely, Yura

2 3

DELIVERY REPORTS ABOUT YOUR E-MAIL
by bdawes＠acm.org 02 Feb '07

02 Feb '07

The original message was included as attachment

1 0

Re: [boost] [typeof] on TPL suffix
by Steven Watanabe 02 Feb '07

02 Feb '07

AMDG Alexander Nasonov wrote: > TPL suffixes are sometimes inconvenient. I implemented a wrapper > that derives from BOOST_TYPEOF(wrap(something)) in emulation mode. > > The wrap function is > > template<class T> mpl::identity<T> wrap(T&); > > It's somewhat similar to BOOST_TYPEOF_NESTED_TYPEDEF but not a > replacement for it. Is there any interest in my idea? I'm not quite sure how what you are doing helps. typename is required inside a template and illegal outside of one. In Christ, Steven Watanabe

2 1

[Report] 415 regressions on RC_1_34_0 (2007-02-01)
by Douglas Gregor 02 Feb '07

02 Feb '07

Boost Regression test failures Report time: 2007-02-01T14:03:12Z 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… The following platforms have a large number of failures: intel-linux-9.0 415 failures in 24 libraries (35 are from non-broken platforms) algorithm/string (1 of 2 failures are from non-broken platforms) bind (1) config (0 of 1 failures are from non-broken platforms) date_time (0 of 21 failures are from non-broken platforms) dynamic_bitset (1) filesystem (2 of 4 failures are from non-broken platforms) function (1) graph (0 of 2 failures are from non-broken platforms) iostreams (0 of 4 failures are from non-broken platforms) iterator (2) math (1) multi_index (0 of 1 failures are from non-broken platforms) numeric/interval (7) parameter (0 of 1 failures are from non-broken platforms) program_options (0 of 7 failures are from non-broken platforms) ptr_container (0 of 1 failures are from non-broken platforms) python (1 of 63 failures are from non-broken platforms) regex (2 of 36 failures are from non-broken platforms) serialization (0 of 215 failures are from non-broken platforms) spirit (2 of 7 failures are from non-broken platforms) statechart (0 of 2 failures are from non-broken platforms) test (11 of 22 failures are from non-broken platforms) thread (1 of 8 failures are from non-broken platforms) wave (2 of 5 failures are from non-broken platforms) Test failures marked with a (*) represent tests that failed on platforms that are considered broken. They are likely caused by misconfiguration by the regression tester or a failure in a core library such as Test or Config. |algorithm/string| regex: intel-linux-9.0* replace: msvc-8.0 |bind| mem_fn_eq_test: msvc-8.0 |config| config_link_test: intel-linux-9.0* |date_time| testdate_dll: intel-linux-9.0* testdate_duration_dll: intel-linux-9.0* testdate_facet_new_dll: intel-linux-9.0* testdate_input_facet_dll: intel-linux-9.0* testdate_iterator_dll: intel-linux-9.0* testfacet_dll: intel-linux-9.0* testformatters_dll: intel-linux-9.0* testgenerators_dll: intel-linux-9.0* testgreg_cal_dll: intel-linux-9.0* testgreg_day_dll: intel-linux-9.0* testgreg_durations_dll: intel-linux-9.0* testgreg_month_dll: intel-linux-9.0* testgreg_serialize: intel-linux-9.0* testgreg_serialize_dll: intel-linux-9.0* testgreg_serialize_xml: intel-linux-9.0* testgreg_year_dll: intel-linux-9.0* testperiod_dll: intel-linux-9.0* testtime_serialize: intel-linux-9.0* testtime_serialize_std_config: intel-linux-9.0* testtime_serialize_xml: intel-linux-9.0* testtime_serialize_xml_std_config: intel-linux-9.0* |dynamic_bitset| dyn_bitset_unit_tests2: borland-5.8.2 |filesystem| operations_test_dll: intel-linux-9.0* path_test: msvc-8.0 path_test_dll: intel-linux-9.0* msvc-8.0 |function| contains_test: msvc-8.0 |graph| graphviz_test: intel-linux-9.0* serialize: intel-linux-9.0* |iostreams| bzip2_test: intel-linux-9.0* gzip_test: intel-linux-9.0* regex_filter_test: intel-linux-9.0* zlib_test: intel-linux-9.0* |iterator| filter_iterator_test: msvc-8.0 lvalue_concept_fail: msvc-8.0 |math| complex_test: msvc-8.0 |multi_index| test_serialization: intel-linux-9.0* |numeric/interval| det: msvc-8.0 integer: msvc-8.0 mul: msvc-8.0 overflow: msvc-8.0 pi: msvc-8.0 pow: msvc-8.0 test_float: msvc-8.0 |parameter| python_test: intel-linux-9.0* |program_options| cmdline_test_dll: intel-linux-9.0* options_description_test_dll: intel-linux-9.0* parsers_test_dll: intel-linux-9.0* positional_options_test_dll: intel-linux-9.0* unicode_test_dll: intel-linux-9.0* variable_map_test_dll: intel-linux-9.0* winmain_dll: intel-linux-9.0* |ptr_container| serialization: intel-linux-9.0* |python| andreas_beyer: intel-linux-9.0* args: intel-linux-9.0* auto_ptr: intel-linux-9.0* back_reference: intel-linux-9.0* bases: intel-linux-9.0* ben_scott1: intel-linux-9.0* bienstman1: intel-linux-9.0* bienstman2: intel-linux-9.0* bienstman3: intel-linux-9.0* builtin_converters: intel-linux-9.0* callbacks: intel-linux-9.0* const_argument: intel-linux-9.0* crossmod_exception: intel-linux-9.0* crossmod_opaque: intel-linux-9.0* data_members: intel-linux-9.0* defaults: intel-linux-9.0* dict: intel-linux-9.0* docstring: intel-linux-9.0* enum: intel-linux-9.0* exception_translator: intel-linux-9.0* exec: msvc-8.0 extract: intel-linux-9.0* implicit: intel-linux-9.0* injected: intel-linux-9.0* iterator: intel-linux-9.0* keywords: intel-linux-9.0* list: intel-linux-9.0* long: intel-linux-9.0* map_indexing_suite: intel-linux-9.0* minimal: intel-linux-9.0* multi_arg_constructor: intel-linux-9.0* nested: intel-linux-9.0* numpy: intel-linux-9.0* object: intel-linux-9.0* opaque: intel-linux-9.0* operators: intel-linux-9.0* pearu1: intel-linux-9.0* pickle1: intel-linux-9.0* pickle2: intel-linux-9.0* pickle3: intel-linux-9.0* pickle4: intel-linux-9.0* pointee: intel-linux-9.0* pointer_type_id_test: intel-linux-9.0* pointer_vector: intel-linux-9.0* polymorphism: intel-linux-9.0* polymorphism2: intel-linux-9.0* polymorphism2_auto_ptr: intel-linux-9.0* properties: intel-linux-9.0* raw_ctor: intel-linux-9.0* return_arg: intel-linux-9.0* shared_ptr: intel-linux-9.0* slice: intel-linux-9.0* staticmethod: intel-linux-9.0* stl_iterator: intel-linux-9.0* str: intel-linux-9.0* test_pointer_adoption: intel-linux-9.0* try: intel-linux-9.0* tuple: intel-linux-9.0* upcast: intel-linux-9.0* vector_indexing_suite: intel-linux-9.0* virtual_functions: intel-linux-9.0* voidptr: intel-linux-9.0* wrapper_held_type: intel-linux-9.0* |regex| bad_expression_test: intel-linux-9.0* captures_example: intel-linux-9.0* captures_test: intel-linux-9.0* credit_card_example: intel-linux-9.0* icu_example: intel-linux-9.0* mfc_example: intel-linux-9.0* object_cache_test: intel-linux-9.0* partial_regex_grep: intel-linux-9.0* partial_regex_match: intel-linux-9.0* posix_api_check: intel-linux-9.0* posix_api_check_cpp: intel-linux-9.0* recursion_test: intel-linux-9.0* regex_dll_config_info: intel-linux-9.0* regex_grep_example_1: intel-linux-9.0* regex_grep_example_2: intel-linux-9.0* regex_grep_example_3: intel-linux-9.0* regex_grep_example_4: intel-linux-9.0* regex_iterator_example: intel-linux-9.0* regex_match_example: intel-linux-9.0* regex_merge_example: intel-linux-9.0* regex_regress_dll: intel-linux-9.0* regex_regress_threaded: intel-linux-9.0* msvc-8.0 regex_replace_example: intel-linux-9.0* regex_search_example: intel-linux-9.0* regex_split_example_1: intel-linux-9.0* regex_split_example_2: intel-linux-9.0* regex_timer: intel-linux-9.0* regex_token_iterator_eg_1: intel-linux-9.0* regex_token_iterator_eg_2: intel-linux-9.0* static_mutex_test: intel-linux-9.0* test_collate_info: intel-linux-9.0* test_grep: intel-linux-9.0* sun-5.8 unicode_iterator_test: intel-linux-9.0* wide_posix_api_check_cpp: intel-linux-9.0* |serialization| test_array_binary_archive_dll: intel-linux-9.0* test_array_text_archive_dll: intel-linux-9.0* test_array_text_warchive_dll: intel-linux-9.0* test_array_xml_archive_dll: intel-linux-9.0* test_array_xml_warchive_dll: intel-linux-9.0* test_binary_binary_archive_dll: intel-linux-9.0* test_binary_text_archive_dll: intel-linux-9.0* test_binary_text_warchive_dll: intel-linux-9.0* test_binary_xml_archive_dll: intel-linux-9.0* test_binary_xml_warchive_dll: intel-linux-9.0* test_class_info_load_binary_archive_dll: intel-linux-9.0* test_class_info_load_text_archive_dll: intel-linux-9.0* test_class_info_load_text_warchive_dll: intel-linux-9.0* test_class_info_load_xml_archive_dll: intel-linux-9.0* test_class_info_load_xml_warchive_dll: intel-linux-9.0* test_class_info_save_binary_archive_dll: intel-linux-9.0* test_class_info_save_text_archive_dll: intel-linux-9.0* test_class_info_save_text_warchive_dll: intel-linux-9.0* test_class_info_save_xml_archive_dll: intel-linux-9.0* test_class_info_save_xml_warchive_dll: intel-linux-9.0* test_contained_class_binary_archive_dll: intel-linux-9.0* test_contained_class_text_archive_dll: intel-linux-9.0* test_contained_class_text_warchive_dll: intel-linux-9.0* test_contained_class_xml_archive_dll: intel-linux-9.0* test_contained_class_xml_warchive_dll: intel-linux-9.0* test_cyclic_ptrs_binary_archive_dll: intel-linux-9.0* test_cyclic_ptrs_text_archive_dll: intel-linux-9.0* test_cyclic_ptrs_text_warchive_dll: intel-linux-9.0* test_cyclic_ptrs_xml_archive_dll: intel-linux-9.0* test_cyclic_ptrs_xml_warchive_dll: intel-linux-9.0* test_delete_pointer_binary_archive_dll: intel-linux-9.0* test_delete_pointer_text_archive_dll: intel-linux-9.0* test_delete_pointer_text_warchive_dll: intel-linux-9.0* test_delete_pointer_xml_archive_dll: intel-linux-9.0* test_delete_pointer_xml_warchive_dll: intel-linux-9.0* test_demo_auto_ptr_dll: intel-linux-9.0* test_demo_dll: intel-linux-9.0* test_demo_exception_dll: intel-linux-9.0* test_demo_fast_archive_dll: intel-linux-9.0* test_demo_pimpl_dll: intel-linux-9.0* test_demo_polymorphic_dll: intel-linux-9.0* test_demo_portable_archive_dll: intel-linux-9.0* test_demo_shared_ptr_dll: intel-linux-9.0* test_demo_xml_dll: intel-linux-9.0* test_demo_xml_load_dll: intel-linux-9.0* test_demo_xml_save_dll: intel-linux-9.0* test_deque_binary_archive_dll: intel-linux-9.0* test_deque_text_archive_dll: intel-linux-9.0* test_deque_text_warchive_dll: intel-linux-9.0* test_deque_xml_archive_dll: intel-linux-9.0* test_deque_xml_warchive_dll: intel-linux-9.0* test_derived_binary_archive_dll: intel-linux-9.0* test_derived_class_binary_archive_dll: intel-linux-9.0* test_derived_class_ptr_binary_archive_dll: intel-linux-9.0* test_derived_class_ptr_text_archive_dll: intel-linux-9.0* test_derived_class_ptr_text_warchive_dll: intel-linux-9.0* test_derived_class_ptr_xml_archive_dll: intel-linux-9.0* test_derived_class_ptr_xml_warchive_dll: intel-linux-9.0* test_derived_class_text_archive_dll: intel-linux-9.0* test_derived_class_text_warchive_dll: intel-linux-9.0* test_derived_class_xml_archive_dll: intel-linux-9.0* test_derived_class_xml_warchive_dll: intel-linux-9.0* test_derived_text_archive_dll: intel-linux-9.0* test_derived_text_warchive_dll: intel-linux-9.0* test_derived_xml_archive_dll: intel-linux-9.0* test_derived_xml_warchive_dll: intel-linux-9.0* test_diamond_binary_archive_dll: intel-linux-9.0* test_diamond_text_archive_dll: intel-linux-9.0* test_diamond_text_warchive_dll: intel-linux-9.0* test_diamond_xml_archive_dll: intel-linux-9.0* test_diamond_xml_warchive_dll: intel-linux-9.0* test_exported_binary_archive_dll: intel-linux-9.0* test_exported_text_archive_dll: intel-linux-9.0* test_exported_text_warchive_dll: intel-linux-9.0* test_exported_xml_archive_dll: intel-linux-9.0* test_exported_xml_warchive_dll: intel-linux-9.0* test_list_binary_archive_dll: intel-linux-9.0* test_list_ptrs_binary_archive_dll: intel-linux-9.0* test_list_ptrs_text_archive_dll: intel-linux-9.0* test_list_ptrs_text_warchive_dll: intel-linux-9.0* test_list_ptrs_xml_archive_dll: intel-linux-9.0* test_list_ptrs_xml_warchive_dll: intel-linux-9.0* test_list_text_archive_dll: intel-linux-9.0* test_list_text_warchive_dll: intel-linux-9.0* test_list_xml_archive_dll: intel-linux-9.0* test_list_xml_warchive_dll: intel-linux-9.0* test_map_binary_archive_dll: intel-linux-9.0* test_map_text_archive_dll: intel-linux-9.0* test_map_text_warchive_dll: intel-linux-9.0* test_map_xml_archive_dll: intel-linux-9.0* test_map_xml_warchive_dll: intel-linux-9.0* test_mi_binary_archive_dll: intel-linux-9.0* test_mi_text_archive_dll: intel-linux-9.0* test_mi_text_warchive_dll: intel-linux-9.0* test_mi_xml_archive_dll: intel-linux-9.0* test_mi_xml_warchive_dll: intel-linux-9.0* test_mult_archive_types_dll: intel-linux-9.0* test_multiple_ptrs_binary_archive_dll: intel-linux-9.0* test_multiple_ptrs_text_archive_dll: intel-linux-9.0* test_multiple_ptrs_text_warchive_dll: intel-linux-9.0* test_multiple_ptrs_xml_archive_dll: intel-linux-9.0* test_multiple_ptrs_xml_warchive_dll: intel-linux-9.0* test_no_rtti_binary_archive_dll: intel-linux-9.0* test_no_rtti_text_archive_dll: intel-linux-9.0* test_no_rtti_text_warchive_dll: intel-linux-9.0* test_no_rtti_xml_archive_dll: intel-linux-9.0* test_no_rtti_xml_warchive_dll: intel-linux-9.0* test_non_default_ctor2_binary_archive_dll: intel-linux-9.0* test_non_default_ctor2_text_archive_dll: intel-linux-9.0* test_non_default_ctor2_text_warchive_dll: intel-linux-9.0* test_non_default_ctor2_xml_archive_dll: intel-linux-9.0* test_non_default_ctor2_xml_warchive_dll: intel-linux-9.0* test_non_default_ctor_binary_archive_dll: intel-linux-9.0* test_non_default_ctor_text_archive_dll: intel-linux-9.0* test_non_default_ctor_text_warchive_dll: intel-linux-9.0* test_non_default_ctor_xml_archive_dll: intel-linux-9.0* test_non_default_ctor_xml_warchive_dll: intel-linux-9.0* test_non_intrusive_binary_archive_dll: intel-linux-9.0* test_non_intrusive_text_archive_dll: intel-linux-9.0* test_non_intrusive_text_warchive_dll: intel-linux-9.0* test_non_intrusive_xml_archive_dll: intel-linux-9.0* test_non_intrusive_xml_warchive_dll: intel-linux-9.0* test_null_ptr_binary_archive_dll: intel-linux-9.0* test_null_ptr_text_archive_dll: intel-linux-9.0* test_null_ptr_text_warchive_dll: intel-linux-9.0* test_null_ptr_xml_archive_dll: intel-linux-9.0* test_null_ptr_xml_warchive_dll: intel-linux-9.0* test_nvp_binary_archive_dll: intel-linux-9.0* test_nvp_text_archive_dll: intel-linux-9.0* test_nvp_text_warchive_dll: intel-linux-9.0* test_nvp_xml_archive_dll: intel-linux-9.0* test_nvp_xml_warchive_dll: intel-linux-9.0* test_object_binary_archive_dll: intel-linux-9.0* test_object_text_archive_dll: intel-linux-9.0* test_object_text_warchive_dll: intel-linux-9.0* test_object_xml_archive_dll: intel-linux-9.0* test_object_xml_warchive_dll: intel-linux-9.0* test_optional_binary_archive_dll: intel-linux-9.0* test_optional_text_archive_dll: intel-linux-9.0* test_optional_text_warchive_dll: intel-linux-9.0* test_optional_xml_archive_dll: intel-linux-9.0* test_optional_xml_warchive_dll: intel-linux-9.0* test_polymorphic_binary_archive_dll: intel-linux-9.0* test_polymorphic_text_archive_dll: intel-linux-9.0* test_polymorphic_text_warchive_dll: intel-linux-9.0* test_polymorphic_xml_archive_dll: intel-linux-9.0* test_polymorphic_xml_warchive_dll: intel-linux-9.0* test_primitive_binary_archive_dll: intel-linux-9.0* test_primitive_text_archive_dll: intel-linux-9.0* test_primitive_text_warchive_dll: intel-linux-9.0* test_primitive_xml_archive_dll: intel-linux-9.0* test_primitive_xml_warchive_dll: intel-linux-9.0* test_private_ctor_dll: intel-linux-9.0* test_recursion_binary_archive_dll: intel-linux-9.0* test_recursion_text_archive_dll: intel-linux-9.0* test_recursion_text_warchive_dll: intel-linux-9.0* test_recursion_xml_archive_dll: intel-linux-9.0* test_recursion_xml_warchive_dll: intel-linux-9.0* test_registered_binary_archive_dll: intel-linux-9.0* test_registered_text_archive_dll: intel-linux-9.0* test_registered_text_warchive_dll: intel-linux-9.0* test_registered_xml_archive_dll: intel-linux-9.0* test_registered_xml_warchive_dll: intel-linux-9.0* test_reset_object_address_dll: intel-linux-9.0* test_set_binary_archive_dll: intel-linux-9.0* test_set_text_archive_dll: intel-linux-9.0* test_set_text_warchive_dll: intel-linux-9.0* test_set_xml_archive_dll: intel-linux-9.0* test_set_xml_warchive_dll: intel-linux-9.0* test_shared_ptr_132_binary_archive_dll: intel-linux-9.0* test_shared_ptr_132_text_archive_dll: intel-linux-9.0* test_shared_ptr_132_text_warchive_dll: intel-linux-9.0* test_shared_ptr_132_xml_archive_dll: intel-linux-9.0* test_shared_ptr_132_xml_warchive_dll: intel-linux-9.0* test_shared_ptr_binary_archive_dll: intel-linux-9.0* test_shared_ptr_text_archive_dll: intel-linux-9.0* test_shared_ptr_text_warchive_dll: intel-linux-9.0* test_shared_ptr_xml_archive_dll: intel-linux-9.0* test_shared_ptr_xml_warchive_dll: intel-linux-9.0* test_simple_class_binary_archive_dll: intel-linux-9.0* test_simple_class_ptr_binary_archive_dll: intel-linux-9.0* test_simple_class_ptr_text_archive_dll: intel-linux-9.0* test_simple_class_ptr_text_warchive_dll: intel-linux-9.0* test_simple_class_ptr_xml_archive_dll: intel-linux-9.0* test_simple_class_ptr_xml_warchive_dll: intel-linux-9.0* test_simple_class_text_archive_dll: intel-linux-9.0* test_simple_class_text_warchive_dll: intel-linux-9.0* test_simple_class_xml_archive_dll: intel-linux-9.0* test_simple_class_xml_warchive_dll: intel-linux-9.0* test_split_binary_archive_dll: intel-linux-9.0* test_split_text_archive_dll: intel-linux-9.0* test_split_text_warchive_dll: intel-linux-9.0* test_split_xml_archive_dll: intel-linux-9.0* test_split_xml_warchive_dll: intel-linux-9.0* test_tracking_binary_archive_dll: intel-linux-9.0* test_tracking_text_archive_dll: intel-linux-9.0* test_tracking_text_warchive_dll: intel-linux-9.0* test_tracking_xml_archive_dll: intel-linux-9.0* test_tracking_xml_warchive_dll: intel-linux-9.0* test_unregistered_binary_archive_dll: intel-linux-9.0* test_unregistered_text_archive_dll: intel-linux-9.0* test_unregistered_text_warchive_dll: intel-linux-9.0* test_unregistered_xml_archive_dll: intel-linux-9.0* test_unregistered_xml_warchive_dll: intel-linux-9.0* test_variant_binary_archive_dll: intel-linux-9.0* test_variant_text_archive_dll: intel-linux-9.0* test_variant_text_warchive_dll: intel-linux-9.0* test_variant_xml_archive_dll: intel-linux-9.0* test_variant_xml_warchive_dll: intel-linux-9.0* test_vector_binary_archive_dll: intel-linux-9.0* test_vector_text_archive_dll: intel-linux-9.0* test_vector_text_warchive_dll: intel-linux-9.0* test_vector_xml_archive_dll: intel-linux-9.0* test_vector_xml_warchive_dll: intel-linux-9.0* test_void_cast_dll: intel-linux-9.0* |spirit| bug_000008: intel-linux-9.0* grammar_mt_tests: intel-linux-9.0* owi_mt_tests: intel-linux-9.0* scoped_lock_tests: intel-linux-9.0* scoped_lock_tests_debug: intel-linux-9.0* symbols_add_null: msvc-8.0 symbols_add_null_debug: msvc-8.0 |statechart| DllTestNative: intel-linux-9.0* DllTestNormal: intel-linux-9.0* |test| boost_check_equal_str: intel-linux-9.0* msvc-6.5 errors_handling_test: intel-linux-9.0* msvc-6.5 fixed_mapping_test: intel-linux-9.0* msvc-6.5 ifstream_line_iterator_test: intel-linux-9.0* msvc-6.5 output_test_stream_test: intel-linux-9.0* msvc-6.5 parameterized_test_test: intel-linux-9.0* msvc-6.5 prg_exec_fail3: cw-9.4 msvc-8.0 result_report_test: intel-linux-9.0* msvc-6.5 test_case_template_test: intel-linux-9.0* msvc-6.5 test_fp_comparisons: intel-linux-9.0* test_tools_test: intel-linux-9.0* msvc-6.5 token_iterator_test: intel-linux-9.0* |thread| test_barrier: intel-linux-9.0* test_condition: intel-linux-9.0* test_mutex: intel-linux-9.0* test_once: intel-linux-9.0* test_thread: intel-linux-9.0* test_tss: intel-linux-9.0* test_tss_lib: msvc-8.0 test_xtime: intel-linux-9.0* |wave| test_re2c_lexer: intel-linux-9.0* test_slex_lexer: intel-linux-9.0* testwave: msvc-8.0 testwave_dll: intel-linux-9.0* sun-5.8

2 1

Boost.Accumulators Review
by Javier Estrada 01 Feb '07

01 Feb '07

Eric, I've the following documentation comments: In user_s_guide.html#accumulators.user_s_guide.the_accumulators_framework ------------------- Missing indeterminate article: The first sentence in The Accumulators Framework reads: "The Accumulators Framework is framework..." Should read: "The Accumulators Framework is a framework..." ------------------- Typo: cacheing for caching The sentence in the last bullet in The Accumulators Framework section reads: "...resolving dependencies between requested calculations, possibly cacheing intermediate results" Should read: "...resolving dependencies between requested calculations, possibly caching intermediate results" ------------------- Typo: calcualte for calculate The C++ comment in the code below section Passing Optional Parameters reads: // This will calcualte the left tail and my_order_variate for N == 2 Should read: // This will calculate the left tail and my_order_variate for N == 2 ------------------- Inconsistency: No hyperlink for external<> In the Accumulators Toolbox section, the table cell that contains external<> does not have a hyperlink ------------------- Typo: are for is In Extending the Accumulators Framework section, the sentence that reads: Also covered are how to control the dependency resolution of features within an accumulator set. Should read: Also covered is how to control the dependency resolution of features within an accumulator set. ------------------- Typo: explanitory for explanatory In Extending the Accumulators Framework section, the sentence that reads: Much of the above should be pretty self-explanitory Should read: Much of the above should be pretty self-explanatory ------------------- Typo: double be In the Defining a New Feature section, the sentence: The result of mpl::apply< impl, sample-type, weight-type >::type must be be the type of the accumulator that implements this feature. Should read: The result of mpl::apply< impl, sample-type, weight-type >::type must be the type of the accumulator that implements this feature. ------------------- Regards, Javier

3 2

[graph] leda_graph.hpp
by Jens Müller 01 Feb '07

01 Feb '07

Hi all, I looked at the leda_graph.hpp and made the following changes: * property map interface to the LEDA edge_array class nearly 1:1 copy of node_array stuff * adapter for non-templated 'graph' class added nearly 1:1 copy of code for GRAPH<vtype,etype> * fixed access functions (outside iterator code) to use member functions of the graph/GRAPH class see http://www.algorithmic-solutions.info/leda_manual/graph.html * replaced leda_something by leda::something (node, edge) * make iterators use 'public' LEDA interfaces see http://www.algorithmic-solutions.info/leda_manual/graph.html * implemented clear_vertex * implemented EdgeListGraph concept * edge_iterator class * edges function Still have to test them, though, and clarify copyright stuff with my boss. I have one question about leda_graph_id_map: Is the id() member function for nodes (and edges) officially defined somewhere? Jens

2 5

Re: [boost] shmem map tutorial
by Ion Gaztañaga 01 Feb '07

01 Feb '07

Hi Jan Jan Stetka wrote: > I've put together a tutorial on how to use interprocess map. > > Its at > http://myweb.tiscali.co.uk/janstetka/interprocess_map.html > > Perhaps there could be a link from the interprocesses documentation if > it goes down well. > > Thanks Nice work. I will include your help as an example in the next version of Interprocess' documentation. Ion

1 0

Re: [boost] Request for interest in new library : Bit Logic
by Art Stamness 01 Feb '07

01 Feb '07

(oops hit reply-to-sender, not list ) Begin forwarded message: > From: Art Stamness <artstamness(a)yahoo.com> > Date: January 31, 2007 5:11:21 PM PST > To: me22 <me22.ca(a)gmail.com> > Subject: Re: [boost] Request for interest in new library : Bit Logic > > On Jan 31, 2007, at 4:21 PM, me22 wrote: > >> On 1/31/07, Art Stamness <artstamness(a)yahoo.com> wrote: >>> Any feedback, positive, negative, suggestions is always appreciated. >>> Also if there is a better suggestion for a name, I am open to it. I >>> realize the Boost.Logic library has a very different purpose than >>> this one, and don't want them to be confused. >>> >> Boost.Bitwise, maybe? >> >> Typo: http://www.emulogic.com/bit_logic/bit_vector/index.html >> "middle of the container is dones in" > > Thanks, corrected now. > >> Regarding the implementation, smallest_bit_storage would probably be >> better off using Boost.Integer's facilities or a trick like is using >> in uint_t to avoid requiring the specifically-sized types. > > Those types are limited by the largest integral type of the system. > This library is intended for modeling small and large types. I > should have made it more clear in the examples in the > documentation. Ex. a bit_array<100> is a perfectly valid type. > while a boost::int_t<100> is not. > >> However, what's the main advantage of your code over >> Boost.Dynamic_Bitset and std::bitset? It seems (from a quick look) >> that your bit_array is close to std::bitset and your bit_vector is >> close to at least one of dynamic_bitset and vector<bool> (the latter >> being specialised for packing). > > True, these types are similar to the std::bitset / > boost::dynamic_bitset / std::vector<bool> in that they are used to > represent bit data. However they have a very different operational > semantic. These types are intended to model bit containers for > arbitrary logic functions. Things that are commonly found when > modeling hardware systems ( you can find why i do this under the > "Motivation" section ). > > For instance, taking 4 bits from one type and 4 bits from another, > doing a logical exclusive-or on those bits, and placing it in 4 > bits of a third type is a 1 line operation. > > c.select(15,12) = a.select(7,4) ^ b.select(3,0) ; // a,b,c can all > be bit_array / bit_vector / bit_container ( adapted type ) > > This very closely mimics what is found in hardware description > languages ( which is my background ) . > > c[15:12] = a[7:4] ^ b[3:0] ; // Same operation in Verilog > > This library is intended to provide fixed , and resizable types, > that can be used to model n-bit long logical operations in a clear > semantic description, while also providing some STL container like > interface for use with STL algorithm. > > The above listed operations would be very difficult to do with any > of the 3 listed types. > > Thank you for taking the time to look and comment, I hope I have > answered your questions. > > -Art >

2 2

[thread] regressions for msvc-8.0 x64
by Roland Schwarz 01 Feb '07

01 Feb '07

I am unsure how this "regression" should be handled. Since this _is_ a new compiler it is not really a regression, but on the other hand the compilers toolset name is the same as for x32. 1) Is there a way to explicitly markup as expected to fail conditioned on x64 ? 2) I do not have yet an x64 compiler so I will not be able to implement the tss cleanup for static linking for 1.34. I'll do this later. Roland

2 2

Re: [boost] whitespace and user-defined types in lexical_cast
by Alexander Nasonov 01 Feb '07

01 Feb '07

30.01.07, 21:03, John Salmon <john(a)thesalmons.org>: > The patch satisfies that test on my system (Linux, gcc-3.3.3). I was > surprised that such a test was not already in the regression suite. > Something like it obviously should be, so I added some very similar > tests just to be sure. These are in the original patch: Thanks. I'll add them. > Yes. There have been a few discussions over the years. There are two > basic themes: > 1 - somebody thinks that lexical_cast ought to work on a type whose > operator>> isn't smart enough to handle a non-default skipws flag. > The response is typically "your operator>> is broken", followed by > more or less discussion about whether lexical_cast should accommodate > "broken" operator>> anyway. We are repeating this theme. > 2 - a desire for consistency between the handling of leading > whitespace and trailing whitespace. > I would suggest that the fact that questions of type 1 keep coming up > is an indication that the current behavior is surprising and > alternatives should be explored. If we can change it so that it is > less surprising to "newbies" without breaking anything else and > without introducing new complexity, I think we should. OK. > I would suggest that the answer to questions of type 2 is to observe > that it's not trailing whitespace that causes the exception, it's > trailing *anything*. As such, it should be clearly documented. In > fact, the proposed text for the specification of lexical_cast in TR2 > makes this very clear. I'll make sure it's documented in boost. > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1973.html Thanks for reminding me of this text. I found few inconsistencies with the boost documentation. -- Alexander Nasonov

1 0