June 2005 - Boost - lists.preview.boost.org

[parameter] concept names
by Cromwell Enage 06 Jul '05

06 Jul '05

I've been browsing the reference.rst file in the CVS tree. Is there a difference between "Keyword Tuple" and "Argument Tuple"? If not, then I believe "Argument Map" be a better name, since some of the expression semantics (and their runtime complexities) are similar to those of a map. Accordingly, I would change "Index Expression" to "Keyword Expression" and "Index Default Expression" to "Keyword Default Expression". A person reading "Index Expression" for the first time might think it was a specialized "Integral Constant Expression". Let me know if I'm missing anything. Cromwell D. Enage __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

5 11

[regex] Clearing failures in regex_regress on Tru64/CXX
by Markus Schöpflin 06 Jul '05

06 Jul '05

Attached patch clears the current failures in regex_regress on Tru64/CXX. Basically it adds an explicit instantiation of a template class needed because otherwise CXX ends up with multiple instances of the static variable used in the class, which is because of the template compilation model chosen for the compiler. As it shouldn't hurt other compilers, I didn't wrap it in #if ... #endif. Secondly it avoids three tricky test cases which hang the test program otherwise. Ok to commit? Markus Index: regress/info.hpp =================================================================== RCS file: /cvsroot/boost/boost/libs/regex/test/regress/info.hpp,v retrieving revision 1.3 diff -u -w -r1.3 info.hpp --- regress/info.hpp 21 Jan 2005 17:26:27 -0000 1.3 +++ regress/info.hpp 28 Jun 2005 12:52:13 -0000 @@ -140,6 +140,11 @@ : public test_info_base<char> {}; +// Explicit instantiations to avoid trouble with multiple instances +// of static variables in the test_info_base class. +template struct test_info_base<wchar_t>; +template struct test_info_base<char>; + template <class charT> std::ostream& operator<<(std::ostream& os, const test_info<charT>&) { Index: regress/test_tricky_cases.cpp =================================================================== RCS file: /cvsroot/boost/boost/libs/regex/test/regress/test_tricky_cases.cpp,v retrieving revision 1.4 diff -u -w -r1.4 test_tricky_cases.cpp --- regress/test_tricky_cases.cpp 30 Mar 2005 11:38:51 -0000 1.4 +++ regress/test_tricky_cases.cpp 28 Jun 2005 12:52:13 -0000 @@ -256,10 +256,12 @@ TEST_REGEX_SEARCH_W(L"[[:unicode:]]+", perl, L"a\x0300\x0400z", match_default, make_array(1, 3, -2, -2)); TEST_REGEX_SEARCH_W(L"[\x10-\xff]", perl, L"\x0300\x0400", match_default, make_array(-2, -2)); TEST_REGEX_SEARCH_W(L"[\01-\05]{5}", perl, L"\x0300\x0400\x0300\x0400\x0300\x0400", match_default, make_array(-2, -2)); +#if !BOOST_WORKAROUND(__DECCXX_VER, BOOST_TESTED_AT(60590042)) TEST_REGEX_SEARCH_W(L"[\x300-\x400]+", perl, L"\x0300\x0400\x0300\x0400\x0300\x0400", match_default, make_array(0, 6, -2, -2)); TEST_REGEX_SEARCH_W(L"[\\x{300}-\\x{400}]+", perl, L"\x0300\x0400\x0300\x0400\x0300\x0400", match_default, make_array(0, 6, -2, -2)); TEST_REGEX_SEARCH_W(L"\\x{300}\\x{400}+", perl, L"\x0300\x0400\x0400\x0400\x0400\x0400", match_default, make_array(0, 6, -2, -2)); #endif +#endif // finally try some case insensitive matches: TEST_REGEX_SEARCH("0123456789@abcdefghijklmnopqrstuvwxyz\\[\\\\\\]\\^_`ABCDEFGHIJKLMNOPQRSTUVWXYZ\\{\\|\\}", perl|icase, "0123456789@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}", match_default, make_array(0, 72, -2, -2)); TEST_REGEX_SEARCH("a", perl|icase, "A", match_default, make_array(0, 1, -2, -2));

4 14

RE: [boost] Re: Customer Friendlier Boost Installation
by Martin Bonner 05 Jul '05

05 Jul '05

----Original Message---- From: Jason Earl [mailto:Jason@hybd.net] Sent: 25 May 2005 15:32 To: boost(a)lists.boost.org Subject: Re: [boost] Re: Customer Friendlier Boost Installation > I think a lot of Windows users are too used to things just working > out of the box, and give up if things don't work like that. If you change that to "A lot of Windows users are used to things just working out of the box, and give up if things don't work like that", you have it exactly right. What is wrong with such expectation? > > As for understanding what targets are etc, I think most developers > will know what targets are. I don't. If you use the Microsoft IDE, you never use the term. [snip] > Maybe it would be good to have some control over build verbosity > (there probably already is some, I just haven't looked yet), Maybe > logging the build info to a file would be better and then logging > errors, messages etc to the screen (and maybe a separate) log file. What people REALLY want, is to download headers + pre-built binaries. If they can't have that, then next best is a pretty gui which asks them all the questions (with the right defaults), and just works. If they can't have that, then really good documentation is required, and I don't think boost is there yet. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

14 38

RE: [boost] Re: Customer Friendlier Boost Installation
by Brian Braatz 05 Jul '05

05 Jul '05

Wild thought- Is there a rational way to have a "environment" checker. I am NOT a bjam expert- but it would be handy if we had some cmd line program that would follow spit out all the info BJAM looks for and finds. I am slightly half cocked in this idea, but basically it would have to be enough information that you could get a better sense for what Bjam was doing Something like C:\boost\> boostenvcheck.exe ** Enviroment Report** Python is not in the path User-config.jam file is setup to use gcc, vc7.1 Etc.... I have been using boost for (has it been that long) 2 years now. Bjam still confounds me. ( I appreciate the work effort, it is a cool tool, I remain struggling with it though) (I am also a tad frustrated because I have been trying to make vc7.1 build wave for the last 5 hours) Semi-Related: I proposed (a long time ago) building a SIMPLE gui framework- with the core elements, and then making a "boost environment checker" out of that- I.e. imagine a tree control with all the types of settings and what nots, and the ability to navigate this gui to try to determine what is not set correctly. > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Lars Gullik Bjønnes > Sent: Thursday, May 26, 2005 3:27 AM > To: boost(a)lists.boost.org > Subject: [boost] Re: Customer Friendlier Boost Installation > > "Hendrik Schober" <SpamTrap(a)gmx.de> writes: > > | Lars Gullik Bjønnes <larsbj(a)gullik.net> wrote: > >> David Abrahams <dave(a)boost-consulting.com> writes: > >> > >> | We never wanted to be the sole province of experts. We always wanted > >> | widespread usage. If you want to be a member of an exclusive > >> | "experts" club this is the wrong place to find it. > >> > >> Sure. But there, imho, must be a difference expected between _users_ > >> of the libraries, and _installers_ (or packagers) of the libraries. > > > > > | How so? Shall people employ an administrator to > | install the libs they want to check out? > > No. But IMHO it should be expect that it is a bit harder to install > (and in this case it is build as well) the library than use it. > > So: Create an windows installer and then the user can use that. > > -- > Lgb > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

7 13

Boost regression notification (2005-06-30)
by Douglas Gregor 05 Jul '05

05 Jul '05

Boost regression test failures ------------------------------ Report time: 2005-06-30T05:35:19Z 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. random preprocessor io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 353 failures in 14 libraries: bind (1) io (2) iterator (2) numeric/ublas (21) preprocessor (1) program_options (12) python (56) random (3) regex (2) serialization (236) spirit (5) test (6) thread (2) wave (4) |bind| mem_fn_eq_test: intel-win32-8_1 |io| ios_state_unit_test: intel-win32-8_1 intel-win32-8_1 |iterator| filter_iterator_test: intel-win32-8_1 lvalue_concept_fail: intel-win32-8_1 |numeric/ublas| concepts: cw-9_4 cw-9_4 cw-9_5-darwin test1: cw-9_4 cw-9_4 cw-9_5-darwin test2: cw-9_4 cw-9_4 cw-9_5-darwin test3: cw-9_4 cw-9_4 cw-9_5-darwin test4: cw-9_4 cw-9_4 cw-9_5-darwin test5: cw-9_4 cw-9_4 cw-9_5-darwin test6: cw-9_4 cw-9_4 cw-9_5-darwin |preprocessor| seq: cw-8_3 |program_options| cmdline_test: vc-7_0 cmdline_test_dll: mingw-3_4_2 vc-7_0 parsers_test: vc-7_0 parsers_test_dll: vc-7_0 positional_options_test_dll: mingw-3_4_2 unicode_test: vc-7_0 unicode_test_dll: cw-9_5-darwin gcc-3_3-darwin vc-7_0 variable_map_test: vc-7_0 variable_map_test_dll: vc-7_0 |python| andreas_beyer: intel-win32-8_1 args: intel-win32-8_1 auto_ptr: intel-win32-8_1 back_reference: intel-win32-8_1 ben_scott1: intel-win32-8_1 bienstman1: intel-win32-8_1 bienstman2: intel-win32-8_1 bienstman3: intel-win32-8_1 builtin_converters: intel-win32-8_1 callbacks: intel-win32-8_1 const_argument: intel-win32-8_1 crossmod_exception: intel-win32-8_1 data_members: intel-win32-8_1 defaults: intel-win32-8_1 dict: intel-win32-8_1 docstring: intel-win32-8_1 embedding: intel-win32-8_1 enum: intel-win32-8_1 exception_translator: intel-win32-8_1 extract: gcc-3.3.6-linux intel-win32-8_1 implicit: intel-win32-8_1 injected: intel-win32-8_1 iterator: intel-win32-8_1 keywords: intel-win32-8_1 list: gcc-3.3.6-linux intel-win32-8_1 long: intel-win32-8_1 map_indexing_suite: intel-win32-8_1 minimal: intel-win32-8_1 multi_arg_constructor: intel-win32-8_1 nested: intel-win32-8_1 object: intel-win32-8_1 opaque: intel-win32-8_1 operators: gcc-3.3.6-linux intel-win32-8_1 pearu1: intel-win32-8_1 pickle1: intel-win32-8_1 pickle2: intel-win32-8_1 pickle3: intel-win32-8_1 pickle4: intel-win32-8_1 polymorphism: intel-win32-8_1 polymorphism2: intel-win32-8_1 properties: intel-win32-8_1 raw_ctor: intel-win32-8_1 return_arg: intel-win32-8_1 shared_ptr: intel-win32-8_1 slice: gcc-3.3.6-linux intel-win32-8_1 staticmethod: intel-win32-8_1 str: intel-win32-8_1 test_pointer_adoption: intel-win32-8_1 try: intel-win32-8_1 tuple: intel-win32-8_1 vector_indexing_suite: intel-win32-8_1 virtual_functions: intel-win32-8_1 |random| random_test: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 |regex| regex_regress: intel-win32-8_1 regex_regress_dll: intel-win32-8_1 |serialization| test_array_text_archive_dll: cw-9_5-darwin test_array_text_warchive_dll: cw-9_5-darwin test_array_xml_archive_dll: cw-9_5-darwin test_array_xml_warchive_dll: cw-9_5-darwin test_binary_text_archive_dll: cw-9_5-darwin test_binary_text_warchive_dll: cw-9_5-darwin test_binary_xml_archive_dll: cw-9_5-darwin test_binary_xml_warchive_dll: cw-9_5-darwin test_class_info_load_binary_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_binary_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-6_5 test_class_info_load_xml_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_save_text_archive_dll: cw-9_5-darwin test_class_info_save_text_warchive_dll: cw-9_5-darwin test_class_info_save_xml_warchive_dll: cw-9_5-darwin test_const_load_fail1: borland-5_6_4 test_const_load_fail1_nvp: borland-5_6_4 test_const_load_fail2: borland-5_6_4 test_const_load_fail2_nvp: borland-5_6_4 test_const_save_fail1: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail2: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail3: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_contained_class_text_archive_dll: cw-9_5-darwin test_contained_class_text_warchive_dll: cw-9_5-darwin test_contained_class_xml_archive_dll: cw-9_5-darwin test_contained_class_xml_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_text_archive_dll: cw-9_5-darwin test_cyclic_ptrs_text_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_archive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_warchive_dll: cw-9_5-darwin test_delete_pointer_text_archive_dll: cw-9_5-darwin test_delete_pointer_text_warchive_dll: cw-9_5-darwin test_delete_pointer_xml_archive_dll: cw-9_5-darwin test_delete_pointer_xml_warchive_dll: cw-9_5-darwin test_demo: intel-win32-8_1 test_demo_auto_ptr_dll: cw-9_5-darwin test_demo_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_exception: intel-win32-8_1 test_demo_exception_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_fast_archive_dll: msvc vc-6_5 test_demo_pimpl_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_demo_polymorphic_dll: cw-9_5-darwin test_demo_portable_archive: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 vc-7_0 vc-7_1 vc-8_0 test_demo_portable_archive_dll: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 test_demo_shared_ptr: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_shared_ptr_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-7_0 test_demo_xml_load: intel-win32-8_1 test_demo_xml_save: intel-win32-8_1 test_deque_text_archive_dll: cw-9_5-darwin test_deque_text_warchive_dll: cw-9_5-darwin test_deque_xml_archive_dll: cw-9_5-darwin test_deque_xml_warchive_dll: cw-9_5-darwin test_derived_class_ptr_text_archive_dll: cw-9_5-darwin test_derived_class_ptr_text_warchive_dll: cw-9_5-darwin test_derived_class_ptr_xml_archive_dll: cw-9_5-darwin test_derived_class_ptr_xml_warchive_dll: cw-9_5-darwin test_derived_class_text_archive_dll: cw-9_5-darwin test_derived_class_text_warchive_dll: cw-9_5-darwin test_derived_class_xml_archive_dll: cw-9_5-darwin test_derived_class_xml_warchive_dll: cw-9_5-darwin test_derived_text_archive_dll: cw-9_5-darwin test_derived_text_warchive_dll: cw-9_5-darwin test_derived_xml_warchive_dll: cw-9_5-darwin test_diamond_binary_archive: cw-8_3 cw-9_5-darwin test_diamond_binary_archive_dll: cw-9_5-darwin test_diamond_text_archive: cw-8_3 cw-9_5-darwin test_diamond_text_archive_dll: cw-9_5-darwin test_diamond_text_warchive: cw-8_3 cw-9_5-darwin test_diamond_text_warchive_dll: cw-9_5-darwin test_diamond_xml_archive: cw-8_3 cw-9_5-darwin test_diamond_xml_archive_dll: cw-9_5-darwin test_diamond_xml_warchive: cw-8_3 cw-9_5-darwin test_diamond_xml_warchive_dll: cw-9_5-darwin test_list_ptrs_text_archive_dll: cw-9_5-darwin test_list_ptrs_text_warchive_dll: cw-9_5-darwin test_list_ptrs_xml_archive_dll: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: cw-9_5-darwin test_list_text_archive_dll: cw-9_5-darwin test_list_text_warchive_dll: cw-9_5-darwin test_list_xml_archive_dll: cw-9_5-darwin test_list_xml_warchive_dll: cw-9_5-darwin test_map_binary_archive_dll: msvc vc-6_5 vc-7_0 test_map_text_archive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_text_warchive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_xml_archive_dll: cw-9_5-darwin test_map_xml_warchive_dll: cw-9_5-darwin test_mi_text_warchive_dll: intel-win32-8_1 test_mult_archive_types: cw-9_4 cw-9_4 cw-9_5-darwin test_mult_archive_types_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 test_multiple_ptrs_text_archive_dll: cw-9_5-darwin test_multiple_ptrs_text_warchive_dll: cw-9_5-darwin test_multiple_ptrs_xml_archive_dll: cw-9_5-darwin test_multiple_ptrs_xml_warchive_dll: cw-9_5-darwin test_no_rtti_text_archive_dll: intel-win32-8_1 test_non_default_ctor_text_archive_dll: cw-9_5-darwin test_non_default_ctor_text_warchive_dll: cw-9_5-darwin test_non_default_ctor_xml_archive_dll: cw-9_5-darwin test_non_default_ctor_xml_warchive_dll: cw-9_5-darwin test_non_intrusive_text_archive_dll: cw-9_5-darwin test_non_intrusive_text_warchive_dll: cw-9_5-darwin test_non_intrusive_xml_archive_dll: cw-9_5-darwin test_non_intrusive_xml_warchive_dll: cw-9_5-darwin test_null_ptr_text_archive_dll: cw-9_5-darwin test_null_ptr_text_warchive_dll: cw-9_5-darwin test_null_ptr_xml_warchive_dll: cw-9_5-darwin test_nvp_text_archive_dll: cw-9_5-darwin test_nvp_text_warchive_dll: cw-9_5-darwin test_nvp_xml_archive_dll: cw-9_5-darwin test_nvp_xml_warchive_dll: cw-9_5-darwin test_object_text_warchive_dll: cw-9_5-darwin test_object_xml_warchive_dll: cw-9_5-darwin test_optional_text_archive_dll: cw-9_5-darwin test_optional_text_warchive_dll: cw-9_5-darwin test_optional_xml_archive_dll: cw-9_5-darwin test_optional_xml_warchive_dll: cw-9_5-darwin test_polymorphic_text_archive_dll: cw-9_5-darwin test_polymorphic_text_warchive_dll: cw-9_5-darwin test_polymorphic_xml_archive_dll: cw-9_5-darwin test_polymorphic_xml_warchive_dll: cw-9_5-darwin test_primitive_text_warchive_dll: cw-9_5-darwin test_primitive_xml_warchive_dll: cw-9_5-darwin test_private_ctor_dll: cw-9_5-darwin test_recursion_text_archive_dll: cw-9_5-darwin test_recursion_text_warchive_dll: cw-9_5-darwin test_recursion_xml_archive_dll: cw-9_5-darwin test_recursion_xml_warchive_dll: cw-9_5-darwin test_reset_object_address_dll: cw-9_5-darwin test_set_text_archive_dll: cw-9_5-darwin test_set_text_warchive_dll: cw-9_5-darwin test_set_xml_archive_dll: cw-9_5-darwin test_set_xml_warchive_dll: cw-9_5-darwin test_shared_ptr_132_binary_archive: borland-5_6_4 test_shared_ptr_132_binary_archive_dll: borland-5_6_4 test_shared_ptr_132_text_archive: borland-5_6_4 test_shared_ptr_132_text_archive_dll: borland-5_6_4 test_shared_ptr_132_text_warchive: borland-5_6_4 test_shared_ptr_132_text_warchive_dll: borland-5_6_4 test_shared_ptr_132_xml_archive: borland-5_6_4 test_shared_ptr_132_xml_archive_dll: borland-5_6_4 test_shared_ptr_132_xml_warchive: borland-5_6_4 test_shared_ptr_132_xml_warchive_dll: borland-5_6_4 test_simple_class_ptr_text_archive_dll: cw-9_5-darwin test_simple_class_ptr_text_warchive_dll: cw-9_5-darwin test_simple_class_ptr_xml_archive_dll: cw-9_5-darwin test_simple_class_ptr_xml_warchive_dll: cw-9_5-darwin test_simple_class_text_archive_dll: cw-9_5-darwin test_simple_class_text_warchive_dll: cw-9_5-darwin test_simple_class_xml_archive_dll: cw-9_5-darwin test_simple_class_xml_warchive_dll: cw-9_5-darwin test_split_text_archive_dll: cw-9_5-darwin test_split_text_warchive_dll: cw-9_5-darwin test_split_xml_warchive_dll: cw-9_5-darwin test_tracking_text_archive_dll: cw-9_5-darwin test_tracking_text_warchive_dll: cw-9_5-darwin test_tracking_xml_warchive_dll: cw-9_5-darwin test_variant_text_archive_dll: cw-9_5-darwin test_variant_text_warchive_dll: cw-9_5-darwin test_variant_xml_archive_dll: cw-9_5-darwin test_variant_xml_warchive_dll: cw-9_5-darwin test_vector_text_archive_dll: cw-9_5-darwin test_vector_text_warchive_dll: cw-9_5-darwin test_vector_xml_archive_dll: cw-9_5-darwin test_vector_xml_warchive_dll: cw-9_5-darwin |spirit| bug_fixes: cw-9_5-darwin bug_fixes_debug: cw-9_5-darwin numerics_tests: gcc-3.2.3-linux numerics_tests_debug: gcc-3.2.3-linux owi_mt_tests: gcc-3_3-darwin |test| errors_handling_test: cw-9_5-darwin vc-8_0 test_fp_comparisons: borland-5_6_4 test_tools_test: cw-9_4 cw-9_4 cw-9_5-darwin |thread| test_read_write_mutex: borland-5_6_4 test_thread_lib: cw-8_3 |wave| testwave: cw-8_3 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux

6 9

Interfaces Library, a macro less implementation
by Joel de Guzman 05 Jul '05

05 Jul '05

Hi, I like the idea behind the Interfaces Library: http://www.kangaroologic.com/interfaces/ I need one now. I dislike the macro-based Interface Definition Language, however. I find it utterly ugly especially because interfaces should be immediately readable. IMO, the macro-based IDL is not. Here's another take (prototype) at a macro less implementation of the interfaces (see attached). Tested on VC7.1, g++ and Comeau. The biggest advantage is that the same C++ member function interface syntax is retained. This makes it very easy to understand and even allows documentation extraction tools like Doxygen to work as usual. A disadvantage is that there is some unavoidable redundancy-- a lesser price to pay, IMO. Here's a client side example: struct foo : member_function<int(int)> {}; struct bar : member_function<int(char const*)> {}; // a baz "interface" class baz : interface<foo, bar> { public: template <class T> baz(T& x) : construct(x) {} int foo(int x) { return this->call< ::foo>(x); } int bar(char const* x) { return this->call< ::bar>(x); } }; struct some_baz { int impl(foo, int x) { return x + 1; } int impl(bar, char const* s) { return std::strlen(s); } }; struct another_baz { int impl(foo, int x) { return x - 1; } int impl(bar, char const* s) { return -std::strlen(s); } }; int main() { some_baz f; baz p = f; std::cout << "p.foo(3) = " << p.foo(3) << std::endl; std::cout << "p.bar(\"hi\") = " << p.bar("hi") << std::endl; another_baz f2; p = f2; std::cout << "p.foo(3) = " << p.foo(3) << std::endl; std::cout << "p.bar(\"hi\") = " << p.bar("hi") << std::endl; } Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net #include <iostream> #include <string> #include <cstring> #include <boost/spirit/fusion/sequence/tuple.hpp> #include <boost/spirit/fusion/sequence/at.hpp> using namespace boost::fusion; template <class Sig> struct member_function; template <class RT, class A0> struct member_function<RT(A0)> { typedef RT return_type; typedef A0 arg0_type; typedef RT(*pointer_type)(void*, A0); }; template <class F0, class F1> struct interface { typedef tuple< typename F0::pointer_type , typename F1::pointer_type> vtable_type; template <class T> struct functions { template <typename F> struct forward { typedef typename F::return_type return_type; typedef typename F::arg0_type arg0_type; static return_type call(void* p, arg0_type x) { return static_cast<T*>(p)->impl(F(), x); } }; static typename interface<F0, F1>::vtable_type const* table() { static typename interface<F0, F1>::vtable_type vtable( &forward<F0>::call , &forward<F1>::call); return &vtable; // a singleton } }; template <class T> interface(T& x) : vtable(functions<T>::table()) , obj(&x) {} typedef interface<F0, F1> construct; typename boost::fusion::meta::at_c<vtable_type const, 0>::type find(F0) const { return boost::fusion::at<0>(*vtable); } typename boost::fusion::meta::at_c<vtable_type const, 1>::type find(F1) const { return boost::fusion::at<1>(*vtable); } template <typename F> typename F::return_type call(typename F::arg0_type x) { return find(F())(const_cast<void*>(obj), x); } vtable_type const* vtable; void const* obj; }; /////////////////////////////////////////////////////////////// // // Client Code // /////////////////////////////////////////////////////////////// struct foo : member_function<int(int)> {}; struct bar : member_function<int(char const*)> {}; // a baz "interface" class baz : interface<foo, bar> { public: template <class T> baz(T& x) : construct(x) {} int foo(int x) { return this->call< ::foo>(x); } int bar(char const* x) { return this->call< ::bar>(x); } }; struct some_baz { int impl(foo, int x) { return x + 1; } int impl(bar, char const* s) { return std::strlen(s); } }; struct another_baz { int impl(foo, int x) { return x - 1; } int impl(bar, char const* s) { return -std::strlen(s); } }; int main() { some_baz f; baz p = f; std::cout << "p.foo(3) = " << p.foo(3) << std::endl; std::cout << "p.bar(\"hi\") = " << p.bar("hi") << std::endl; another_baz f2; p = f2; std::cout << "p.foo(3) = " << p.foo(3) << std::endl; std::cout << "p.bar(\"hi\") = " << p.bar("hi") << std::endl; }

11 25

[ANN] xpressive 0.9.3 in boost-sandbox
by Eric Niebler 04 Jul '05

04 Jul '05

<< Background >> xpressive is a TR1 regex work-alike that also accepts regexes as expression templates and lets regexes nest and call each other recursively. << Significant changes since 0.9.2 >> - TR1-style regex_traits interface - Speed enhancements - syntax_option_type::ignore_white_space << Download >> xpressive.zip at: http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler << Docs >> http://boost-sandbox.sf.net/libs/xpressive -- Eric Niebler Boost Consulting www.boost-consulting.com

2 2

Re: [boost] Boost regression notification (2005-06-28)
by JOAQUIN LOPEZ MU?Z 03 Jul '05

03 Jul '05

----- Mensaje original ----- De: Joel de Guzman <joel(a)boost-consulting.com> Fecha: Martes, Junio 28, 2005 8:16 pm Asunto: Re: [boost] Boost regression notification (2005-06-28) > Douglas Gregor wrote: > > Boost regression test failures > > > > |spirit| > > action_tests: vc-6_5 > > action_tests_debug: vc-6_5 > > ast_calc_tests: vc-6_5 > > ast_calc_tests_debug: vc-6_5 > [...] > > traverse_tests: vc-6_5 > > traverse_tests_debug: vc-6_5 > > while_p_as_parser_tests: vc-6_5 > > while_tests: vc-6_5 > > while_tests_debug: vc-6_5 > > Yaiks! What happened? VC6.5 is supposed to be an unsupported > (unusable) compiler for Spirit 1.8.x. > metacomm has begun using the vc-6_5 toolset, which is an alias of the old msvc toolset. Markup in status/explicit-failures-markup.xml has to be duplicated for this alternative name. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

5 4

Formal Review: Typeof
by Andy Little 02 Jul '05

02 Jul '05

The formal review of Arkadiy Vertleyb and Peder Holt's Typeof library begins today, May 20th 2005. The review period will continue until the 30th of May. The proposed Typeof library emulates the functionality of the non-standard 'typeof' operator, and incomplete implementations of decltype and the proposed 'auto' declarator , described in http://www.osl.iu.edu/~jajarvi/publications/papers/decltype_n1478.pdf. It is commonly acknowledged that this type of functionality is sorely needed and should be standardardised in the language. For compliant compilers the library requires some help in the form of registration macros but, because use of typeof is by its nature most likely in generic libraries, it is expected that this can often be done by the library author rather than the user. In some cases the compilers capabilities (by means of extensions and even compiler bugs) have been used to remove the need for registration. However, for portability and in order to test emulation mode on the compilers where it is available but not used by default (VC7.1, GCC etc), #define BOOST_TYPEOF_COMPLIANT [see note *1*]. Testing the emulation is useful, even on compilers that provide a better option, to get a rounded view of the library and its capabilities. I hope you will find time to write a review of the library, which is available at: http://boost-sandbox.sourceforge.net/vault/ , typeof.zip The system has been tested with the following compilers: MSVC 6.5/7.0/7.1/8.0; [see note *1* regarding VC7.0 and VC6.5] GCC 3.4.2 (The following is a quote from : http://www.boost.org/more/formal_review_process.htm ) Here are some questions you might want to answer in your review: What is your evaluation of the design? What is your evaluation of the implementation? What is your evaluation of the documentation? What is your evaluation of the potential usefulness of the library? Did you try to use the library? With what compiler? Did you have any problems? How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? Are you knowledgeable about the problem domain? And finally, every review should answer this question: Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Andy Little Typeof review manager notes: *1* MSVC6.5 and VC7.0 are not supported by the BOOST_TYPEOF_COMPLIANT macro

9 43

[logging] flushing logs
by Greg Landrum 02 Jul '05

02 Jul '05

I'm just getting started with John Torjo's logging library. So far the library looks really useful, but I'm having problems understanding the timing/sequencing of output by the logging objects. I'm trying to get the logs to dump their output to std:cerr immediately: // ----------------------------- #include <iostream> #include <boost/log/log.hpp> #include <boost/log/functions.hpp> namespace logging = boost::logging; BOOST_DECLARE_LOG(cerrLog); BOOST_DEFINE_LOG(cerrLog,"cerrLog"); void write_to_cerr(const std::string &, const std::string &msg) { std::cerr << msg; std::cerr.flush();} int main(){ logging::add_modifier("cerrLog",logging::prepend_time("[$hh:$mm:$ss] "), logging::DEFAULT_INDEX-10); logging::add_appender("cerrLog",write_to_cerr,logging::DEFAULT_INDEX+1); std::cerr << "1" << std::endl; BOOST_LOG(cerrLog) << "2" << std::endl; std::cerr << "3" << std::endl; BOOST_LOG(cerrLog) << "4" << std::endl; } // ----------------------------- However, the output from running this is always something like: 1 3 [14:56:35] 2 [14:56:35] 4 So the logger output is "late". Is there some flag I can set (or appender I can use) that will force output to go to the target streams immediately or is this outside the design of the logging library? In the event that it matters: I'm using version 1.33 of the logging library and I've tested this on both Windows (vs .net 2003) and Linux (g++ v3.2). Thanks, -greg

3 3