- Boost - lists.boost.org

Why does not boost::mem_fn declare arg-types for arity > 2?
by Marcus Lindblom 12 Sep '06

12 Sep '06

Hi, I would really like that feature, as the current implementation forces me to create a bogus boost::function-type to pass along just to be able to handle argument types properly. Comments? /Marcus

1 0

[Boost-bugs] [ boost-Patches-1557285 ] opaque_pointer bug fix + enhancement
by SourceForge.net 12 Sep '06

12 Sep '06

Patches item #1557285, was opened at 2006-09-12 17:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1557285&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: Gottfried Gan�auge (ganssauge) Assigned to: Nobody/Anonymous (nobody) Summary: opaque_pointer bug fix + enhancement Initial Comment: After debugging a crash I found out that all instances created from opaque_pointer_converter had a type object which itself didn't have a type, and this finally lead to the crash. The attached patch corrects this behaviour by initialising the type object using PyType_Ready(). Furthermore I implemented cross module support in so far as the converter registers itself only if not another module already has registered the same converter before. The opaque test case has been update to check for the segmentation fault mentioned in my previous post. A test case for the cross module support is included (crossmod_opaque). I also updated the documentation for opaque. I tested my patch with - GCC-4.1 running on GNU/Linux 2.6.16.21-0.13-default x86_64 - Visual-C++-6.5 running on Windows XP - Visual-C++-7.1 running on Windows XP The patch is applied by calling patch -p1 < opaque_patch in the root of the boost hierarchy. Files patched are: boost_head/boost/python/opaque_pointer_converter.hpp boost_head/libs/python/doc/v2/opaque.html boost_head/libs/python/doc/v2/opaque_pointer_converter.html boost_head/libs/python/doc/v2/reference.html boost_head/libs/python/doc/v2/return_opaque_pointer.html boost_head.orig/libs/python/test/crossmod_opaque_a.cpp boost_head/libs/python/test/crossmod_opaque_a.cpp boost_head/libs/python/test/crossmod_opaque_b.cpp boost_head/libs/python/test/crossmod_opaque.py boost_head/libs/python/test/Jamfile boost_head/libs/python/test/Jamfile.v2 boost_head/libs/python/test/opaque.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1557285&group_… ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost inspection notification (2006-09-12/RC_1_34_0) *X*
by Rene Rivera 12 Sep '06

12 Sep '06

Boost Inspection Report Run Date: 16:03:26 UTC, Tuesday 12 September 2006 An inspection program <http://www.boost.org/tools/inspect/index.html> checks each file in the current Boost CVS for various problems, generating this as output. Problems detected include tabs in files, missing copyrights, broken URL's, and similar misdemeanors. Totals: 11659 files scanned 903 directories scanned 194 problems reported Problem counts: 0 files with invalid line endings 0 bookmarks with invalid characters 3 invalid urls 109 broken links 29 unlinked files 8 file names too long 0 files with tabs 3 violations of the Boost min/max guidelines 42 usages of unnamed namespaces in headers (including .ipp files) Summary: archive (3) bind (1) build (4) date_time (1) doc (2) filesystem (36) graph (4) iostreams (2) iterator (7) lambda (3) libs (6) more (12) mpl (1) multi_array (2) numeric (2) parameter (5) ptr_container (1) regex (1) regression (13) serialization (1) spirit (2) test (79) thread (3) type_traits (1) typeof (2) Details: *R* invalid (cr only) line-ending *A* invalid bookmarks, invalid urls, broken links, unlinked files *N* file names too long *T* tabs in file *M* uses of min and max that have not been protected from the min/max macros *U* unnamed namespace in header |archive| boost/archive/basic_streambuf_locale_saver.hpp: *N* filename > 31 chars boost/archive/impl/xml_wiarchive_impl.ipp: *U* unnamed namespace at line 53 boost/archive/iterators/remove_whitespace.hpp: *U* unnamed namespace at line 57 |bind| boost/bind/placeholders.hpp: *U* unnamed namespace at line 25 |build| tools/build/v1/variables.html: *A* unlinked file tools/build/v2/example/libraries/util/foo/include/lib1.h: *N* file's directory depth will exceed 8 levels if placed on a CD tools/build/v2/example/make/main.cpp.pro: *N* filename contains more than one dot character ('.') tools/build/v2/test/test_system.html: *A* unlinked file |date_time| libs/date_time/xmldoc/date_time_docs_howto.html: *A* unlinked file |doc| doc/html/boost_math/inverse_complex.html: *A* unlinked file doc/html/jam.html: *A* unlinked file |filesystem| libs/filesystem/doc/do-list.htm: *A* invalid URL (hardwired file): file://?/ *A* invalid URL (hardwired file): file://?/UNC/ libs/filesystem/doc/i18n.html: *A* broken link: convenience.htm#basic_recursive_directory_iterator *A* broken link: exception.htm *A* broken link: operations.htm *A* broken link: operations.htm#Do-the-right-thing *A* broken link: operations.htm#is_directory *A* broken link: operations.htm#is_file *A* broken link: operations.htm#status libs/filesystem/doc/index.htm: *A* broken link: convenience.htm *A* broken link: fstream.htm *A* broken link: operations.htm#create_directory *A* broken link: operations.htm#create_hard_link *A* broken link: operations.htm#current_path *A* broken link: operations.htm#directory_iterator *A* broken link: operations.htm#equivalent *A* broken link: operations.htm#file_size *A* broken link: operations.htm#initial_path *A* broken link: operations.htm#is_file *A* broken link: operations.htm#is_symlink *A* broken link: operations.htm#status *A* broken link: operations.htm#symlink_status *A* broken link: path.htm#Canonical *A* broken link: path.htm#Grammar *A* broken link: path.htm#Normalized *A* broken link: path.htm#default_name_check *A* broken link: path.htm#name_check_mechanism *A* broken link: path.htm#normalize *A* broken link: path.htm#operator_eq *A* broken link: path.htm#synopsis libs/filesystem/doc/portability_guide.htm: *A* broken link: path.htm#name_check_typedef libs/filesystem/doc/tr2_proposal.html: *A* invalid URL (hardwired file): file:///C|/boost/site/libs/filesystem/doc/operations.htm#complete_note |graph| boost/graph/maximum_cardinality_matching.hpp: *M* violation of Boost min/max guidelines on line 755 *N* filename > 31 chars libs/graph/doc/lengauer_tarjan_dominator_tree.htm: *N* filename > 31 chars libs/graph/doc/sorted_erdos_renyi_generator.html: *N* filename > 31 chars |iostreams| libs/iostreams/doc/acknowledgments.html: *A* unlinked file libs/iostreams/doc/concepts/multi-character.html: *A* unlinked file |iterator| libs/iterator/doc/filter_iterator_ref.html: *A* unlinked file libs/iterator/doc/indirect_iterator_ref.html: *A* unlinked file libs/iterator/doc/issues.html: *A* unlinked file libs/iterator/doc/iter-issue-list.html: *A* unlinked file libs/iterator/doc/iterator_adaptor_ref.html: *A* unlinked file libs/iterator/doc/make_filter_iterator.html: *A* unlinked file libs/iterator/doc/ref_problem.html: *A* unlinked file |lambda| boost/lambda/core.hpp: *U* unnamed namespace at line 62 boost/lambda/detail/lambda_functors.hpp: *U* unnamed namespace at line 25 boost/lambda/exceptions.hpp: *U* unnamed namespace at line 24 |libs| libs/libraries.htm: *A* broken link: math/octonion/index.html *A* broken link: math/quaternion/index.html *A* broken link: math/special_functions/index.html |more| more/feature_model_diagrams.htm: *A* broken link: FeatureDescriptions more/version_history.html: *A* broken link: ../doc/html/date_time/date_time_io.html *A* broken link: ../doc/html/date_time/details.html#date_time.changes *A* broken link: ../doc/html/date_time/local_time.html *A* broken link: ../libs/math/octonion/index.html *A* broken link: ../libs/math/quaternion/index.html *A* broken link: ../libs/math/special_functions/index.html |mpl| boost/mpl/alias.hpp: *U* unnamed namespace at line 17 |multi_array| boost/multi_array/base.hpp: *U* unnamed namespace at line 69 libs/multi_array/test/generative_tests.hpp: *U* unnamed namespace at line 57 |numeric| boost/numeric/conversion/detail/old_numeric_cast.hpp: *M* violation of Boost min/max guidelines on line 159 *M* violation of Boost min/max guidelines on line 192 |parameter| libs/parameter/doc/html/index.html: *A* broken link: ../../../libs/bind/index.html *A* broken link: ../../../property_map/doc/ReadWritePropertyMap.html *A* broken link: ../../../property_map/doc/ReadablePropertyMap.html *A* broken link: tag::index *A* broken link: tag::name |ptr_container| libs/ptr_container/doc/tutorial_example.html: *A* unlinked file |regex| libs/regex/performance/input.html: *A* unlinked file |regression| regression/.htaccess: *N* leading character of one of the path compontents is not alphabetic tools/regression/xsl_reports/xsl/html/issues_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/library_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/library_user_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/make_tinyurl.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/summary_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/summary_user_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/issues_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/library_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/library_user_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/make_tinyurl.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_user_legend.html: *A* unlinked file |serialization| libs/serialization/src/basic_xml_grammar.ipp: *U* unnamed namespace at line 43 |spirit| boost/spirit/utility/rule_parser.hpp: *U* unnamed namespace at line 70 libs/spirit/test/impl/string_length.hpp: *U* unnamed namespace at line 16 |test| boost/test/floating_point_comparison.hpp: *U* unnamed namespace at line 206 *U* unnamed namespace at line 228 boost/test/impl/cpp_main.ipp: *U* unnamed namespace at line 42 boost/test/impl/exception_safety.ipp: *U* unnamed namespace at line 400 boost/test/impl/framework.ipp: *U* unnamed namespace at line 199 boost/test/impl/plain_report_formatter.ipp: *U* unnamed namespace at line 45 boost/test/impl/progress_monitor.ipp: *U* unnamed namespace at line 38 boost/test/impl/results_collector.ipp: *U* unnamed namespace at line 106 boost/test/impl/results_reporter.ipp: *U* unnamed namespace at line 48 boost/test/impl/unit_test_log.ipp: *U* unnamed namespace at line 79 boost/test/impl/unit_test_monitor.ipp: *U* unnamed namespace at line 35 boost/test/impl/unit_test_parameters.ipp: *U* unnamed namespace at line 50 boost/test/results_collector.hpp: *U* unnamed namespace at line 40 boost/test/test_tools.hpp: *U* unnamed namespace at line 255 boost/test/utils/iterator/token_iterator.hpp: *U* unnamed namespace at line 166 boost/test/utils/named_params.hpp: *U* unnamed namespace at line 216 boost/test/utils/runtime/cla/dual_name_parameter.ipp: *U* unnamed namespace at line 43 boost/test/utils/runtime/cla/modifier.hpp: *U* unnamed namespace at line 34 boost/test/utils/runtime/env/modifier.hpp: *U* unnamed namespace at line 34 boost/test/utils/runtime/file/config_file.hpp: *U* unnamed namespace at line 169 *U* unnamed namespace at line 64 *U* unnamed namespace at line 74 boost/test/utils/runtime/file/config_file_iterator.hpp: *U* unnamed namespace at line 68 boost/test/utils/trivial_singleton.hpp: *U* unnamed namespace at line 52 *U* unnamed namespace at line 61 libs/test/build/msvc71_proj/config_file_iterator_test.vcproj: *N* filename > 31 chars libs/test/doc/components/prg_exec_monitor/index.html: *A* broken link: ../../../../../boost/test/cpp_main.hpp libs/test/doc/components/test_tools/index.html: *A* broken link: ../../tests/boost_check_equal_str.html libs/test/doc/components/test_tools/reference/BOOST_CHECK_CLOSE.html: *A* broken link: BOOST_CHECK_CLOSE_FRACTION.html libs/test/doc/components/test_tools/reference/BOOST_CHECK_MESSAGE.html: *A* broken link: BOOST_MESSAGE.html libs/test/doc/components/test_tools/reference/BOOST_CHECK_SMALL.html: *A* broken link: BOOST_CHECK_CLOSE_FRACTION.html libs/test/doc/components/test_tools/reference/tools_list.html: *A* broken link: ../../btl1.gif *A* broken link: BOOST_CHECK_CLOSE_FRACTION.html libs/test/doc/components/utf/components/index.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/components/test_case/abstract_interface.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/auto_register_facility.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/boost_function_tc.html: *A* broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/class_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/function_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/param_boost_function_tc.html: *A* broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/param_class_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/param_function_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/tc_template.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_log/custom_log_formatter.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_log/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_result/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_suite/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/index.html: *A* broken link: getting_started/index.html libs/test/doc/components/utf/parameters/build_info.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/catch_system_errors.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/detect_memory_leaks.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/index.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/log_format.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/log_level.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/no_result_code.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/output_format.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/random.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/report_format.html: *A* broken link: ../../../../../LICENSE_1_0.txt *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/report_level.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/show_progress.html: *A* broken link: ../../btl1.gif libs/test/doc/examples/unit_test_example1.html: *A* broken link: ../../example/unit_test_example1.cpp libs/test/doc/examples/unit_test_example2.html: *A* broken link: ../../example/unit_test_example2.cpp libs/test/doc/examples/unit_test_example3.html: *A* broken link: ../../example/unit_test_example3.cpp libs/test/doc/examples/unit_test_example4.html: *A* broken link: ../../example/unit_test_example4.cpp libs/test/doc/examples/unit_test_example5.html: *A* broken link: ../../example/unit_test_example5.cpp *A* broken link: ../../example/unit_test_example5.input libs/test/doc/tests/auto_unit_test_test.html: *A* broken link: ../../test/auto_unit_test_test.cpp libs/test/doc/tests/auto_unit_test_test_mult.html: *A* broken link: ../../test/auto_unit_test_test_mult1.cpp *A* broken link: ../../test/auto_unit_test_test_mult2.cpp libs/test/doc/tests/unit_test_suite_ex_test.html: *A* broken link: ../../test/unit_test_suite_ex_test.cpp libs/test/doc/tutorials/hello_the_testing_world.html: *A* broken link: ../../../../../LICENSE_1_0.txt *A* broken link: ../execution_monitor/index.html libs/test/doc/tutorials/new_year_resolution.html: *A* broken link: ../../../../../../LICENSE_1_0.txt |thread| libs/thread/src/mutex.inl: *U* unnamed namespace at line 12 libs/thread/src/timeconv.inl: *U* unnamed namespace at line 12 libs/thread/test/util.inl: *U* unnamed namespace at line 24 |type_traits| libs/type_traits/cxx_type_traits.htm: *A* unlinked file |typeof| boost/typeof/encode_decode.hpp: *U* unnamed namespace at line 13 libs/typeof/test/odr.hpp: *U* unnamed namespace at line 12

1 0

Boost regression notification (2006-09-12 [RC_1_34_0])
by Douglas Gregor 12 Sep '06

12 Sep '06

Boost Regression test failures Report time: 2006-09-12T11:30:14Z 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… 161 failures in 17 libraries filesystem (2) graph (4) io (1) iostreams (3) mpl (7) numeric/conversion (4) parameter (21) program_options (9) python (68) random (1) rational (5) serialization (18) signals (8) spirit (4) test (3) tr1 (2) utility (1) |filesystem| mbcopy: sun-5.8 wide_test: sun-5.8 |graph| adjacency_matrix_test: vc-7_0 csr_graph_test: sun-5.8 graphviz_test: intel-vc71-win-9.1 msvc-8.0 |io| ios_state_unit_test: gcc-4.1.0_linux_x86_64 |iostreams| compose_test: borland-5_6_4 example_test: vc-6_5-stlport finite_state_filter_test: cw-9.4 |mpl| multiset: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 sort: gcc-4_0_3_tru64 vector_c: sun-5.8 |numeric/conversion| converter_test: borland-5_8_2 traits_test: borland-5_8_2 udt_example_0: borland-5_8_2 udt_support_test: borland-5_8_2 |parameter| compose: sun-5.8 duplicates: borland-5_6_4 borland-5_8_2 earwicker: sun-5.8 efficiency: sun-5.8 maybe: vc-6_5 vc-6_5-stlport vc-7_0 ntp: sun-5.8 preprocessor: sun-5.8 python-parameter-test: vc-6_5 vc-6_5-stlport vc-7_0 sfinae: borland-5_8_2 vc-6_5-stlport singular: borland-5_6_4 borland-5_8_2 unnamed: sun-5.8 unnamed_fail: vc-6_5 vc-6_5-stlport vc-7_0 |program_options| cmdline_test_dll: cw-9.4 options_description_test_dll: cw-9.4 parsers_test_dll: cw-9.4 positional_options_test_dll: cw-9.4 unicode_test_dll: borland-5_8_2 cw-9.4 variable_map_test_dll: borland-5_8_2 cw-9.4 winmain_dll: cw-9.4 |python| andreas_beyer: cw-9.4 args: cw-9.4 auto_ptr: cw-9.4 back_reference: cw-9.4 ben_scott1: cw-9.4 bienstman1: cw-9.4 bienstman2: cw-9.4 bienstman3: cw-9.4 callbacks: cw-9.4 const_argument: cw-9.4 crossmod_exception: cw-9.4 data_members: cw-9.4 sun-5.8 defaults: cw-9.4 dict: cw-9.4 docstring: cw-9.4 enum: cw-9.4 exception_translator: cw-9.4 exec: darwin-4.0.1 extract: cw-9.4 implicit: cw-9.4 injected: cw-9.4 iterator: cw-9.4 keywords: cw-9.4 list: cw-9.4 long: cw-9.4 minimal: cw-9.4 multi_arg_constructor: cw-9.4 nested: cw-9.4 numpy: cw-9.4 gcc-3.3.6 gcc-3.4.4 sun-5.8 object: cw-9.4 opaque: cw-9.4 operators: cw-9.4 pearu1: cw-9.4 pickle1: cw-9.4 pickle2: cw-9.4 pickle3: cw-9.4 sun-5.8 pickle4: cw-9.4 pointer_vector: cw-9.4 polymorphism: cw-9.4 polymorphism2: cw-9.4 polymorphism2_auto_ptr: cw-9.4 sun-5.8 properties: cw-9.4 raw_ctor: cw-9.4 return_arg: cw-9.4 select_from_python_test: darwin-4.0.1 shared_ptr: cw-9.4 slice: cw-9.4 gcc-3.3.6 gcc-3.4.4 sun-5.8 staticmethod: cw-9.4 stl_iterator: cw-9.4 str: cw-9.4 test_pointer_adoption: cw-9.4 try: cw-9.4 tuple: cw-9.4 vector_indexing_suite: cw-9.4 intel-linux-9.0 virtual_functions: cw-9.4 voidptr: cw-9.4 wrapper_held_type: cw-9.4 sun-5.8 |random| random_test: intel-linux-9.0 |rational| rational_test: borland-5_6_4 sun-5.8 vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_class_info_load_text_warchive: vc-6_5 test_derived_class_xml_warchive_dll: msvc-8.0 test_non_default_ctor2_text_archive: qcc-3.3.5_cpp test_non_default_ctor2_text_archive_dll: qcc-3.3.5_cpp test_non_default_ctor2_text_warchive: qcc-3.3.5_cpp test_non_default_ctor2_text_warchive_dll: qcc-3.3.5_cpp test_registered_xml_archive: msvc-8.0 test_reset_object_address: vc-7_0 test_reset_object_address_dll: vc-7_0 test_simple_class_binary_archive_dll: vc-6_5 test_simple_class_text_archive_dll: vc-6_5 test_simple_class_text_warchive_dll: vc-6_5 test_simple_class_xml_archive_dll: vc-6_5 test_simple_class_xml_warchive_dll: vc-6_5 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| dead_slot_test: gcc-3.3.6 gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_gpp trackable_test: gcc-3.3.6 gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_gpp |spirit| mix_and_match_trees: sun-5.8 switch_tests_general_def: gcc-4.1.0_linux switch_tests_general_def_debug: gcc-4.1.0_linux intel-linux-9.0 |test| algorithms_test: msvc-8.0 parameterized_test_test: vc-6_5 vc-6_5-stlport |tr1| tr1_tky_incomp_type_test: borland-5_6_4 borland-5_8_2 |utility| operators_test: gcc-3.4.5_linux_x86_64

1 0

[Review]{MPI] boostMPI review
by John Phillips 12 Sep '06

12 Sep '06

- What is your evaluation of the design? I like the choice of making it focus on easing the communications tasks using the serialization library. At least for those new to MPI, proper message construction and interpretation is a major hurdle that this greatly reduces. - What is your evaluation of the implementation? Seems solid, but I didn't get very deep into it. - What is your evaluation of the documentation? In need of editing for detail. Numerous typos and some questionable sentence constructions. Also useful would be adding a translation table. For those new to the MPI, a well organized listing of C style MPI functions and the boostMPI equivalent would allow them to translate example code in C to similar code in boostMPI bindings. Since there are a large number of books and online references listing usable code in C and Fortran, but none yet use boost MPI thas would speed adoption of the library. - What is your evaluation of the potential usefulness of the library? I think it will be very useful. As it stands, it can support many reasonable MPI based tasks, and when it has matured to support all of MPI 2, it will be the obvious choice for MPI programming in C++. - Did you try to use the library? With what compiler? Did you have any problems? I did a few simple examples using gcc compilers with a multi-processor Mac box. I also did them on a small cluster of Windows/Cygwin boxes and on a small cluster of Sun boxes. The underlying MPI implementation was OpenMPI for the mac and for the Windows boxes, and LAM/MPI for the Sun boxes. I didn't have any problems. - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? A few hours, so not all that long. I read the docs fairly closely, installed the libraries and wrote, compiled and ran some example code. I have not yet used it in reasearch code, but I am likely to do so in the next few months. - Are you knowledgeable about the problem domain? I'm somewhat knowledgeable. I make use of MPI for research code and I am currently teaching a class on parallel and distributed programming using MPI. I have not used it in industrial settings. The bottom line for me is a request for additions to the documentation, a hope that full MPI 2 support can become a reality soon, and a recomendation that the library be included in boost. John Phillips

2 1

[Review][MPI] Boost.MPI Review
by Dean Michael Berris 12 Sep '06

12 Sep '06

Hi Everyone, I have been lurking a while already, and I'm doing my first review of a Boost library being proposed for inclusion. I would like to say that I'm pretty new at this review thing, and I'm trying to learn about the way it's being done as fast as I can. I certainly hope this review brings out a few points that may make sense, and I also hope the library authors (Doug Gregor and Matthias Troyer) would take the time to consider the points in this message. So here goes the review: Explicitly State My View: YES, I think it should be accepted into Boost. Details and suggestions below. - What is your evaluation of the design? The design is pretty straightforward, and easy to understand even for the novice C++ developer -- which is a welcome characteristic IMO. I certainly appreciate the relatively few headers, and "fat classes" that group together the related methods and data -- citing the Communicator and the Environment classes. - What is your evaluation of the implementation? Given the very well-thought out and straightforward design, I have some reservations about the interface specifically with the Communicator class. Having been reading up on type-safe interfaces, the main issue I see is the relative ease in confusing the order of the fields/types in communicator::send/receive/isend/ireceive arguments: template <typename T> void send(int, int, const T &) const ; The above line doesn't say anything about what the first int is, and what the second int is -- and it's fairly easy to confuse which one is the rank and which one is the tag. A suggestion I would make is either to utilize Boost.Parameter to come up with something like: mpi::communicator c; std::string str("Hello, World!"); c.send(tag=0, rank=1, value=str); c.send(rank=1, tag=0, value=str); c.send(value=str, rank=1, tag=0); Or if that introduces too many issues regarding performance (I'm not sure), then perhaps using some wrappers and overloads for type safety will be useful to allow the following: mpi::communicator c; std::string str("Hello, World!"); c.send(mpi::tag(0), mpi::rank(1), mpi::value(str)); c.send(mpi::rank(1), mpi::tag(0), mpi::value(str)); c.send(mpi::value(str), mpi::tag(0), mpi::rank(1)); The two approaches above would IMO make the library more "idiot-proof" or "newbie-friendly" and certainly (though more tideous to use) considerably type-safe and verbose. - What is your evaluation of the documentation? The web documentation contains certain characters marked and displayed as question marks not present in the PDF version. There are also a handful of typographical errors, though nothing a quick copy-editing would not be able to fix. There is also a need to revise the introduction, and move the in-depth details in a separate section. The Introduction section already talks about a lot of the specifics, when a user reading the documentation would be more concerned really just about what Boost.MPI is rather than the details of how it implemented certain things. I can elaborate in a separate email, which I think I should probably do. - What is your evaluation of the potential usefulness of the library? I think this library will be very useful indeed having been exposed to the mess that is the C implementation of the MPI standard. I've personally tried to tackle with issues like sending and receiving strings and user created data structures (C structs) and the MPI methods are not very helpful nor intuitive in their current form (even MPI 2.0). Being able to introduce an object oriented view of the parallel computing application by encapsulating in objects the MPI interface and adding terse yet expressive interfaces will definitely be helpful in the field. In my experience with academic use of parallel computers (though how very little exposure I have here in the Philippines of that), the biggest barrier to entry is the programming interface. The MPI API's require a lot of patience from even the most experienced C or C++ programmers, and the Boost.MPI interface is a welcome implementation on the change to making it make more sense. Since most of the people I've talked to are in the academe, it would be easier to 1) teach MPI programming with Boost.MPI 2) use the MPI especially for non-computer scientists (Physicists, Mathematicians, Engineers) that might not have the same exposure to C or C++. Since the Boost.MPI interface makes the programs considerably more readable, it should allow for lowering the barrier to entry into parallel and high-performance computing. - Did you try to use the library? No, since I don't have the required libraries and tools (Boost CVS, LAM/MPI 7 for Windows) set up yet. However, I intend to use this library in its current form most probably post-review regardless of the review outcome, and even try to contribute in any way I can (docs, patches, etc.) - How much effort did you put into your evaluation? I have read the documentation, and looked at the design primarily of the library -- and focused on the interface provided. Since I have not had the time nor means for testing the library at the moment, I cannot comment on the implementation especially in terms of the effects in runtime performance and the compile time characteristics. Because of this, I have reserved my comments until the time I can scrutinize the implementation and how it relates to the MPI implementation I shall use. - Are you knowledgable about the problem domain? I have used the MPI C API (LAM/MPI Implementation) in more than one instance in an academic setting (translation: school project on a prallel genetic algorithm implementation for finding the optimal tour in a 100 city travelling salesman problem, thesis on adaptive dynamic allocation algorithm in heterogeneous non-dedicated computing clusters). I would like to think I am knowledgable about the problem domain with ample exposure to the MPI C API (though with MPI 2.0). -- Dean Michael C. Berris C++ Software Architect Orange and Bronze Software Labs, Ltd. Co. web: http://software.orangeandbronze.com/ email: dean(a)orangeandbronze.com mobile: +63 928 7291459 phone: +63 2 8943415 other: +1 408 4049532 blogs: http://mikhailberis.blogspot.com http://3w-agility.blogspot.com http://cplusplus-soup.blogspot.com

5 5

Re: [boost] [asio] SSL operation sporadically returns "Access is denied"
by Christopher Kohlhoff 12 Sep '06

12 Sep '06

Hi Scott, Scott <cheesy4poofs(a)cox.net> wrote: > I made the changes you requested and unfortunately things > aren't any clearer. What I'm seeing now is error_code == > SSL_ERROR_SYSCALL. However, the line I added above: > > int sys_error_code = asio::detail::socket_ops::get_error(); > > sys_error_code == 0 Very odd. > I think I preferred the old way :). Are there any other > changes you would like me to try? I would suggest moving the get_error() line to immediately after the primitive_() call, because I suspect something must be clearing the error. (Unless the SSL_ERROR_SYSCALL itself is misleading and there never really was a system error, but let's not go there unless we have to :) Cheers, Chris

1 0

Interest in a dynamic-state-machine framework?
by Cromwell Enage 12 Sep '06

12 Sep '06

I'm currently Boostifying the FSM module currently located at <http://swiss-gd-knife.sourceforge.net/>. (Yes, that means I'll license the result under the BSL.) I've also implemented a pushdown automaton and will combine the two into a common library. To distinguish this library from Boost.Statechart, I'm treating the state machines as *data structures* to be initialized and manipulated *algorithmically* before normal execution. My primary question is: does anyone have a need for such a library that is not already satisfied by either Boost.Statechart or Boost.Spirit? Off the top of my head, I can think of only two application domains where this library would be useful: artificial intelligence and graph-walking simulations (e.g. mazes). If anyone has another domain in mind, please chime in. I'd like to have a better idea of my potential target audience so I can hone the library design before submitting to the vault. TIA, Cromwell D. Enage __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

[shared_Ptr] [1.34] URGENT: Outstanding HP-UX / itanium bug
by John Maddock 12 Sep '06

12 Sep '06

Folks we still haven't solved the outstanding issue summarised here: http://lists.boost.org/boost-users/2005/12/15692.php Defining BOOST_SP_USE_PTHREADS is at least a workaround. Should I apply this to Boost.Config or should the sp_counted_base.hpp logic be altered (to keep everything in one place)? Or does anyone believe they have a fix for the assembly code in time for 1.34? Thanks, John.

7 21

is_base_and_derived instantiated from within derived class definition
by Zak Kipling 11 Sep '06

11 Sep '06

I have a piece of code which boils down to: ====================================== #include <boost/type_traits/is_base_and_derived.hpp> #include <boost/static_assert.hpp> struct Base { }; template< typename T > struct A { BOOST_STATIC_ASSERT(( boost::is_base_and_derived< Base, T >::value )); struct Inner { }; }; struct Derived : Base { typedef A< Derived >::Inner Inner; }; ======================================= This had been compiling fine with gcc 3.3 up to 4.1.1, but the assertion fails on the current 4.1.2 snapshot as a result of the fix for PR 27177 (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27177) because Derived is incomplete -- although its base class is already known. The failure basically comes down to code like this: ======================================= struct Z {}; struct A : Z {}; Z* implicitToZ (Z*); struct B : A { static const int i = sizeof(implicitToZ((B*)0)); }; ======================================== This compiles up to gcc 4.1.1, and also with Comeau (try pasting it into http://www.comeaucomputing.com/tryitout/) but not with the gcc 4.1.2 snapshot. >From discussion on the above bug page, it appears unclear whether this or not this code is actually legal... has the patch broken something which should be expected to work, or are the existing versions of gcc and Comeau accepting illegal code? Zak.

4 3