- Boost - lists.boost.org

[Review] Reminder xpressive formal review
by Thomas Witt 14 Sep '05

14 Sep '05

Hi, This is to remind everyone of the formal review of Eric Niebler's xpressive library. The review period is scheduled to end Sunday, September 18. I want to especially point out the xpressive is not just another 'regex' library. It goes beyond the scope of regular regex (no pun intended) engines. Here is what Eric has to say: "Although xpressive's primitives are regex-ish in nature, xpressive is far more than just a regular expression engine. It is a pattern matching engine with the power of context-free grammars. By allowing you to embed one pattern in another by reference, xpressive lets you find patterns in data that are recursive in nature. Problems that are intractible with "classic" regular expressions, such as matching balanced nested parentheses or matching XML tags, are simple with xpressive. So xpressive is more rightly thought of as a context-free grammar engine with exhaustive backtracking. The goal is to provide one framework and one set of pattern matching primitives that scales from simple strstr-style grepping, through ordinary regexing, all the way to full-blown parsing." For a glimpse of what xpressive can do look at "Grammars and Nested Matches" here: http://tinyurl.com/d7637 This link takes you to the online docs. The full sources and docs (also in PDF) are available here: http://tinyurl.com/8fean Thomas Review Manager xpressive Thomas Witt witt(a)acm.org

1 0

[regression testing] /libs/numeric/conversion/test/converter_test
by Matt Hurd 14 Sep '05

14 Sep '05

suse linux x86_64 gcc 4.0.1 continues to fail for the following test: /libs/numeric/conversion/test/converter_test Is there a standard way parameterise the python script to avoid this failure. Others seem to run the tests fine looking at the meta-comm site. It is just my zomojo config that fails. regards, matt. matt.hurd(a)zomojo.com _________________________________________________ tail of bjam.log... gcc is in an endless compile MkDir1 /zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test/converter_test.test mkdir "/zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test/converter_test.test" MkDir1 /zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test/converter_test.test/gcc mkdir "/zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test/converter_test.test/gcc" MkDir1 /zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test/converter_test.test/gcc/debug mkdir "/zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test/converter_test.test/gcc/debug" gcc-C++-action /zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test/converter_test.test/gcc/debug/converter_test.o set -e "g++" -c -Wall -ftemplate-depth-255 -g -O0 -fno-inline -I"/zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test" -I "/zomojo/regression_boost/boost" -o "/zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test/converter_test.test/gcc/debug/converter_test.o" "/zomojo/regression_boost/boost/libs/numeric/conversion/test/converter_test.cpp" "/usr/bin/objcopy" --set-section-flags .debug_str=contents,debug "/zomojo/regression_boost/results/bin/boost/libs/numeric/conversion/test/converter_test.test/gcc/debug/converter_test.o"

1 0

Re: [boost] [Review] xpressive - Doc comments
by David Abrahams 14 Sep '05

14 Sep '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > David Abrahams wrote: >> This may have more to do with boostbook/quickbook than with xpressive, but in my >> Windows XP FireFox browser, it appears that every place inline code is >> followed by regular text, there is no space separating them. Spaces >> also seem to be missing in a few other places, e.g. "usingnamespace" >> can be seen on >> http://boost-consulting.com/projects/xpressive/xpressive/user_s_guide.html#…, >> as can "representationof" ("representation" is in italics). So this >> probably applies to all style changes. > > I'm almost sure that I already fixed that a few days ago. Ok, > lemme check... > > Ok, I just confirmed that this bug has been fixed. Eric, please run > the docs using the latest QuickBook from Boost HEAD CVS. > >> Also, the full justification of text is difficult to read. I don't >> think web browsers are smart enough about formatting to make that >> legible, at least not at the normal smallish text sizes. > > Hrmmm. Very subjective. I feel the opposite. Full justification is > better for smaller fonts than bigger fonts because there are more > spaces to allocate and divide. The problem is when there are few > spaces in between text. Well, I don't know the reasons, but Firefox does a fairly poor job of it, at least compared to LaTeX. Well, maybe my biggest complaint has to do with tables, as in http://boost-consulting.com/projects/xpressive/xpressive/creating_a_regex_o… LaTeX does a bad job there, too :) Can you turn off full justification in tables? >> Also, I think the abbrev "parens" should be changed to the word >> "parentheses" :) > > In QuickBook docs? In xpressive? The xpressive docs. But QuickBook too, if you use "parens" there. -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 1

[serialization] cannot build with BOOST_NO_EXCEPTIONS defined
by JOAQUIN LOPEZ MU?Z 14 Sep '05

14 Sep '05

Boost.Serialization tries to be BOOST_NO_EXCEPTIONS-compatible, as it uses boost::throw_exception to throw, but alas the lib does not build when setting the macro, since archive_exception (boost/archive/archive_exception.hpp) is only defined ifndef(BOOST_NO_EXCEPTIONS), so that expressions like boost::throw_exception( archive_exception(archive_exception::unregistered_class)); fail to compile. AFAICS it'd only take for archive_exception to be defined in all cases. Best regards, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Re: [boost] [serialization] No Reply?
by JOAQUIN LOPEZ MU?Z 14 Sep '05

14 Sep '05

----- Mensaje original ----- De: Robert Ramey <ramey(a)rrsd.com> Fecha: Martes, Septiembre 13, 2005 6:10 pm Asunto: Re: [boost] [serialization] No Reply? > This is quite interesting to me. Its going to take a little time > to > consider with the attention it deserves. > > Robert Ramey > > JOAQUIN LOPEZ MU?Z wrote: > > ----- Mensaje original ----- > > De: David Abrahams <dave(a)boost-consulting.com> > > Fecha: Lunes, Septiembre 12, 2005 11:06 pm > > Asunto: Re: [boost] [serialization] No Reply? > > > >> * You should find some way to describe what it means for an input > >> and an output archive to be compatible. Try to do that as > >> formally as possible. You may have to rely on the fuzzy C++ > >> notion of "equivalence," but I wouldn't blame you for that. > > > > IMHO, there's no need to go fuzzy or rely on an undefined > > notion of "equivalence" between a serialized object and > > its restored copy. One can define these concepts with much > > precision in an "operational semantics" way, much as, for > > instance, semantics of logic languages is formally defined: > > > * A type T is serializable if the expressions > > oar<<ct; > > iar>>t; > > are valid, where ct is of type const T& and t is of type T&, > > oar is an output archive and iar is an input archive. > > The above doesn't seem right to me. I don't see its necessary here > an it > makes the concept of serializable and archive circular. I believe > that the > inductive definition below - and currently in the document (more or > less) > defines the concept of serializable well enough. > Hmm... yep, rethinking it, this is superfluous (yet not circular AFAICS): the validity of these expressions is guaranteed by the archive concept as you explain in your docs. Serializability has to be defined in terms of the presence of the serialize function/memfun, as you're doing now. I think there's some weak points in my proposal having to do with the relationship between "archive association" and "restored copy" --for instance, a dummy archive wih accepts iar>>t for every t and simply does nothing would be, according to the definitions, associated with any output archive, and this is clearly not what we want. I've got this thing going round my head, allow me to come back to you in a few days. Best, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

Re: [boost] [Review] xpressive - Doc comments
by Eric Niebler 13 Sep '05

13 Sep '05

Thomas Witt wrote: > Joel de Guzman wrote: > >> David Abrahams wrote: >> >>> This may have more to do with boostbook/quickbook than with >>> xpressive, but in my >>> Windows XP FireFox browser, it appears that every place inline code is >>> followed by regular text, there is no space separating them. Spaces >>> also seem to be missing in a few other places, e.g. "usingnamespace" >>> can be seen on >>> http://boost-consulting.com/projects/xpressive/xpressive/user_s_guide.html#…, >>> >>> as can "representationof" ("representation" is in italics). So this >>> probably applies to all style changes. >> >> >> I'm almost sure that I already fixed that a few days ago. Ok, >> lemme check... >> >> Ok, I just confirmed that this bug has been fixed. Eric, please run >> the docs using the latest QuickBook from Boost HEAD CVS. > > > Hmm... I just confirmed the bug still exists with inline code. CVS Head > of now. This seems to be related to the xml pretty printing. > > Thomas > The bug still exists, confirmed. I have disabled XML pretty printing and regenerated the docs. I've updated the download and put the clean docs at http://boost-sandbox.sf.net/libs/xpressive. (I also took the opportunity to patch a few portability issues in the code.) -- Eric Niebler Boost Consulting www.boost-consulting.com

3 5

CVS Development Status on Boost main page
by Doug Gregor 13 Sep '05

13 Sep '05

I've added the CVS Development Status at the end of the Participation section on the Boost main page. Let's keep this up-to-date so developers know what we're doing without reading the mailing list every day. Doug

1 0

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

13 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-13T18:04:22Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 593 failures in 12 libraries: concept_check (18) foreach (1) graph (22) math (3) mpl (1) multi_index (1) numeric/ublas (1) random (1) range (28) serialization (506) thread (8) wave (3) |concept_check| stl_concept_covering: borland-5_6_4 cw-8_3 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux intel-win32-8_1 mingw-3_4_2 vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 |foreach| rvalue_const: vc-7_1 |graph| betweenness_centrality_test: cw-8_3 gcc-3.4.4-linux gcc-4.0.1-linux gcc-4_0-darwin dag_longest_paths: cw-8_3 gcc-3.4.4-linux gcc-4.0.1-linux gcc-4_0-darwin dijkstra_cc: cw-8_3 gcc-3.4.4-linux gcc-4.0.1-linux gcc-4_0-darwin dijkstra_heap_performance: cw-8_3 gcc-3.4.4-linux gcc-4.0.1-linux gcc-4_0-darwin gursoy_atun_layout_test: cw-8_3 layout_test: cw-8_3 relaxed_heap_test: cw-8_3 gcc-3.4.4-linux gcc-4.0.1-linux gcc-4_0-darwin |math| octonion_test: gcc-4_0-darwin quaternion_test: gcc-4_0-darwin special_functions_test: gcc-4_0-darwin |mpl| size_t: gcc-4_0-darwin |multi_index| test_serialization: intel-win32-9_0 |numeric/ublas| test2: intel-9.0-linux |random| random_test: gcc-3.3.6-linux |range| algorithm_example: vc-6_5 vc-6_5-stlport vc-7_0 array: vc-6_5 vc-6_5-stlport vc-7_0 const_ranges: vc-6_5 vc-6_5-stlport vc-7_0 iterator_pair: cw-8_3 gcc-4_0-darwin vc-6_5 vc-6_5-stlport vc-7_0 partial_workaround: vc-6_5 vc-6_5-stlport vc-7_0 std_container: cw-8_3 gcc-4_0-darwin vc-6_5 vc-6_5-stlport vc-7_0 string: cw-8_3 gcc-4_0-darwin vc-6_5 vc-6_5-stlport vc-7_0 sub_range: vc-6_5 |serialization| test_array_binary_archive: cw-9_5-darwin vc-7_1 test_array_binary_archive_dll: cw-9_5-darwin vc-7_1 test_array_text_archive: cw-9_5-darwin vc-7_1 test_array_text_archive_dll: vc-7_1 test_array_text_warchive: cw-9_5-darwin vc-7_1 test_array_text_warchive_dll: vc-7_1 test_array_xml_archive: cw-9_5-darwin vc-7_1 test_array_xml_archive_dll: vc-7_1 test_array_xml_warchive: cw-9_5-darwin vc-7_1 test_array_xml_warchive_dll: vc-7_1 test_binary_binary_archive: vc-7_1 test_binary_binary_archive_dll: vc-7_1 test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_binary_text_warchive: vc-7_1 test_binary_text_warchive_dll: vc-7_1 test_binary_xml_archive: vc-7_1 test_binary_xml_archive_dll: vc-7_1 test_binary_xml_warchive: vc-7_1 test_binary_xml_warchive_dll: vc-7_1 test_class_info_load_binary_archive: vc-7_1 test_class_info_load_binary_archive_dll: vc-7_1 test_class_info_load_text_archive: vc-7_1 test_class_info_load_text_archive_dll: vc-7_1 test_class_info_load_text_warchive: vc-7_1 test_class_info_load_text_warchive_dll: vc-7_1 test_class_info_load_xml_archive: vc-7_1 test_class_info_load_xml_archive_dll: vc-7_1 test_class_info_load_xml_warchive: vc-7_1 test_class_info_load_xml_warchive_dll: vc-7_1 test_class_info_save_binary_archive: vc-7_1 test_class_info_save_binary_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_class_info_save_text_warchive: vc-7_1 test_class_info_save_text_warchive_dll: vc-7_1 test_class_info_save_xml_archive: vc-7_1 test_class_info_save_xml_archive_dll: vc-7_1 test_class_info_save_xml_warchive: vc-7_1 test_class_info_save_xml_warchive_dll: vc-7_1 test_contained_class_binary_archive: vc-7_1 test_contained_class_binary_archive_dll: vc-7_1 test_contained_class_text_archive: vc-7_1 test_contained_class_text_archive_dll: vc-7_1 test_contained_class_text_warchive: vc-7_1 test_contained_class_text_warchive_dll: vc-7_1 test_contained_class_xml_archive: vc-7_1 test_contained_class_xml_archive_dll: vc-7_1 test_contained_class_xml_warchive: vc-7_1 test_contained_class_xml_warchive_dll: vc-7_1 test_cyclic_ptrs_binary_archive: vc-7_1 test_cyclic_ptrs_binary_archive_dll: vc-7_1 test_cyclic_ptrs_text_archive: vc-7_1 test_cyclic_ptrs_text_archive_dll: vc-7_1 test_cyclic_ptrs_text_warchive: vc-7_1 test_cyclic_ptrs_text_warchive_dll: vc-6_5 vc-7_1 test_cyclic_ptrs_xml_archive: vc-7_1 test_cyclic_ptrs_xml_archive_dll: vc-7_1 test_cyclic_ptrs_xml_warchive: vc-7_1 test_cyclic_ptrs_xml_warchive_dll: vc-6_5 vc-7_1 test_delete_pointer_binary_archive: vc-7_1 test_delete_pointer_binary_archive_dll: vc-7_1 test_delete_pointer_text_archive: vc-7_1 test_delete_pointer_text_archive_dll: vc-7_1 test_delete_pointer_text_warchive: vc-7_1 test_delete_pointer_text_warchive_dll: vc-6_5 vc-7_1 test_delete_pointer_xml_archive: vc-7_1 test_delete_pointer_xml_archive_dll: vc-7_1 test_delete_pointer_xml_warchive: vc-7_1 test_delete_pointer_xml_warchive_dll: vc-6_5 vc-7_1 test_demo: intel-win32-8_1 test_demo_dll: borland-5_6_4 test_demo_exception: intel-win32-8_1 test_demo_exception_dll: borland-5_6_4 test_demo_shared_ptr: intel-win32-8_1 test_demo_shared_ptr_dll: borland-5_6_4 test_demo_xml_dll: borland-5_6_4 test_demo_xml_load: intel-win32-8_1 test_demo_xml_load_dll: borland-5_6_4 test_demo_xml_save: intel-win32-8_1 test_demo_xml_save_dll: borland-5_6_4 test_deque_binary_archive: vc-7_1 test_deque_binary_archive_dll: vc-7_1 test_deque_text_archive: vc-7_1 test_deque_text_archive_dll: vc-7_1 test_deque_text_warchive: vc-7_1 test_deque_text_warchive_dll: vc-7_1 test_deque_xml_archive: vc-7_1 test_deque_xml_archive_dll: vc-7_1 test_deque_xml_warchive: vc-7_1 test_deque_xml_warchive_dll: vc-7_1 test_derived_binary_archive: vc-7_1 test_derived_binary_archive_dll: vc-7_1 test_derived_class_binary_archive: vc-7_1 test_derived_class_binary_archive_dll: vc-7_1 test_derived_class_ptr_binary_archive: vc-7_1 test_derived_class_ptr_binary_archive_dll: vc-7_1 test_derived_class_ptr_text_archive: vc-7_1 test_derived_class_ptr_text_archive_dll: vc-7_1 test_derived_class_ptr_text_warchive: vc-7_1 test_derived_class_ptr_text_warchive_dll: vc-6_5 vc-7_1 test_derived_class_ptr_xml_archive: vc-7_1 test_derived_class_ptr_xml_archive_dll: vc-7_1 test_derived_class_ptr_xml_warchive: vc-7_1 test_derived_class_ptr_xml_warchive_dll: vc-6_5 vc-7_1 test_derived_class_text_archive: vc-7_1 test_derived_class_text_archive_dll: vc-7_1 test_derived_class_text_warchive: vc-7_1 test_derived_class_text_warchive_dll: vc-7_1 test_derived_class_xml_archive: vc-7_1 test_derived_class_xml_archive_dll: vc-7_1 test_derived_class_xml_warchive: vc-7_1 test_derived_class_xml_warchive_dll: vc-7_1 test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_derived_text_warchive: vc-7_1 test_derived_text_warchive_dll: vc-6_5 vc-7_1 test_derived_xml_archive: vc-7_1 test_derived_xml_archive_dll: vc-7_1 test_derived_xml_warchive: vc-7_1 test_derived_xml_warchive_dll: vc-6_5 vc-7_1 test_diamond_binary_archive: vc-7_1 test_diamond_binary_archive_dll: vc-7_1 test_diamond_text_archive: vc-7_1 test_diamond_text_archive_dll: vc-7_1 test_diamond_text_warchive: vc-7_1 test_diamond_text_warchive_dll: vc-7_1 test_diamond_xml_archive: vc-7_1 test_diamond_xml_archive_dll: vc-7_1 test_diamond_xml_warchive: vc-7_1 test_diamond_xml_warchive_dll: vc-7_1 test_exported_binary_archive: vc-6_5 vc-7_1 test_exported_binary_archive_dll: vc-6_5 vc-7_1 test_exported_text_archive: vc-6_5 vc-7_1 test_exported_text_archive_dll: vc-6_5 vc-7_1 test_exported_text_warchive: vc-6_5 vc-7_1 test_exported_text_warchive_dll: vc-6_5 vc-7_1 test_exported_xml_archive: vc-6_5 vc-7_1 test_exported_xml_archive_dll: vc-6_5 vc-7_1 test_exported_xml_warchive: vc-6_5 vc-7_1 test_exported_xml_warchive_dll: vc-6_5 vc-7_1 test_list_binary_archive: vc-7_1 test_list_binary_archive_dll: vc-7_1 test_list_ptrs_binary_archive: vc-7_1 test_list_ptrs_binary_archive_dll: vc-7_1 test_list_ptrs_text_archive: vc-7_1 test_list_ptrs_text_archive_dll: vc-7_1 test_list_ptrs_text_warchive: vc-7_1 test_list_ptrs_text_warchive_dll: vc-6_5 vc-7_1 test_list_ptrs_xml_archive: vc-7_1 test_list_ptrs_xml_archive_dll: vc-7_1 test_list_ptrs_xml_warchive: vc-7_1 test_list_ptrs_xml_warchive_dll: vc-6_5 vc-7_1 test_list_text_archive: vc-7_1 test_list_text_archive_dll: vc-7_1 test_list_text_warchive: vc-7_1 test_list_text_warchive_dll: vc-7_1 test_list_xml_archive: vc-7_1 test_list_xml_archive_dll: vc-7_1 test_list_xml_warchive: vc-7_1 test_list_xml_warchive_dll: vc-7_1 test_map_binary_archive: vc-7_1 test_map_binary_archive_dll: vc-7_1 test_map_text_archive: vc-7_1 test_map_text_archive_dll: vc-7_1 test_map_text_warchive: vc-7_1 test_map_text_warchive_dll: vc-7_1 test_map_xml_archive: vc-6_5 vc-7_0 vc-7_1 test_map_xml_archive_dll: vc-6_5 vc-7_0 vc-7_1 test_map_xml_warchive: vc-6_5 vc-7_0 vc-7_1 test_map_xml_warchive_dll: vc-6_5 vc-7_0 vc-7_1 test_mi_binary_archive: vc-7_1 test_mi_binary_archive_dll: vc-7_1 test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_mi_text_warchive: vc-7_1 test_mi_text_warchive_dll: vc-7_1 test_mi_xml_archive: vc-7_1 test_mi_xml_archive_dll: vc-7_1 test_mi_xml_warchive: vc-7_1 test_mi_xml_warchive_dll: vc-7_1 test_multiple_ptrs_binary_archive: vc-7_1 test_multiple_ptrs_binary_archive_dll: vc-7_1 test_multiple_ptrs_text_archive: vc-7_1 test_multiple_ptrs_text_archive_dll: vc-7_1 test_multiple_ptrs_text_warchive: vc-7_1 test_multiple_ptrs_text_warchive_dll: vc-7_1 test_multiple_ptrs_xml_archive: vc-7_1 test_multiple_ptrs_xml_archive_dll: vc-7_1 test_multiple_ptrs_xml_warchive: vc-7_1 test_multiple_ptrs_xml_warchive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 vc-7_1 test_no_rtti_binary_archive_dll: vc-6_5 vc-7_1 test_no_rtti_text_archive: vc-6_5 vc-7_1 test_no_rtti_text_archive_dll: vc-6_5 vc-7_1 test_no_rtti_text_warchive: vc-6_5 vc-7_1 test_no_rtti_text_warchive_dll: vc-6_5 vc-7_1 test_no_rtti_xml_archive: vc-6_5 vc-7_1 test_no_rtti_xml_archive_dll: vc-6_5 vc-7_1 test_no_rtti_xml_warchive: vc-6_5 vc-7_1 test_no_rtti_xml_warchive_dll: vc-6_5 vc-7_1 test_non_default_ctor2_binary_archive: vc-7_1 test_non_default_ctor2_binary_archive_dll: vc-7_1 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor2_text_warchive: vc-7_1 test_non_default_ctor2_text_warchive_dll: vc-6_5 vc-7_1 test_non_default_ctor2_xml_archive: vc-7_1 test_non_default_ctor2_xml_archive_dll: vc-7_1 test_non_default_ctor2_xml_warchive: vc-7_1 test_non_default_ctor2_xml_warchive_dll: vc-6_5 vc-7_1 test_non_default_ctor_binary_archive: vc-7_1 test_non_default_ctor_binary_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_default_ctor_text_warchive: vc-7_1 test_non_default_ctor_text_warchive_dll: vc-6_5 vc-7_1 test_non_default_ctor_xml_archive: vc-7_1 test_non_default_ctor_xml_archive_dll: vc-7_1 test_non_default_ctor_xml_warchive: vc-7_1 test_non_default_ctor_xml_warchive_dll: vc-6_5 vc-7_1 test_non_intrusive_binary_archive: vc-7_1 test_non_intrusive_binary_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_non_intrusive_text_warchive: vc-7_1 test_non_intrusive_text_warchive_dll: vc-6_5 vc-7_1 test_non_intrusive_xml_archive: vc-7_1 test_non_intrusive_xml_archive_dll: vc-7_1 test_non_intrusive_xml_warchive: vc-7_1 test_non_intrusive_xml_warchive_dll: vc-6_5 vc-7_1 test_null_ptr_binary_archive: vc-7_1 test_null_ptr_binary_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_null_ptr_text_warchive: vc-7_1 test_null_ptr_text_warchive_dll: vc-6_5 vc-7_1 test_null_ptr_xml_archive: vc-7_1 test_null_ptr_xml_archive_dll: vc-7_1 test_null_ptr_xml_warchive: vc-7_1 test_null_ptr_xml_warchive_dll: vc-6_5 vc-7_1 test_nvp_binary_archive: vc-7_1 test_nvp_binary_archive_dll: vc-7_1 test_nvp_text_archive: vc-7_1 test_nvp_text_archive_dll: vc-7_1 test_nvp_text_warchive: vc-7_1 test_nvp_text_warchive_dll: vc-6_5 vc-7_1 test_nvp_xml_archive: vc-7_1 test_nvp_xml_archive_dll: vc-7_1 test_nvp_xml_warchive: vc-7_1 test_nvp_xml_warchive_dll: vc-6_5 vc-7_1 test_object_binary_archive: vc-7_1 test_object_binary_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_object_text_warchive: vc-7_1 test_object_text_warchive_dll: vc-7_1 test_object_xml_archive: vc-7_1 test_object_xml_archive_dll: vc-7_1 test_object_xml_warchive: vc-7_1 test_object_xml_warchive_dll: vc-7_1 test_optional_binary_archive: vc-7_1 test_optional_binary_archive_dll: vc-7_1 test_optional_text_archive: vc-7_1 test_optional_text_archive_dll: vc-7_1 test_optional_text_warchive: vc-7_1 test_optional_text_warchive_dll: vc-7_1 test_optional_xml_archive: vc-7_1 test_optional_xml_archive_dll: vc-7_1 test_optional_xml_warchive: vc-7_1 test_optional_xml_warchive_dll: vc-7_1 test_primitive_binary_archive: vc-7_1 test_primitive_binary_archive_dll: vc-7_1 test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_primitive_text_warchive: vc-7_1 test_primitive_text_warchive_dll: vc-7_1 test_primitive_xml_archive: vc-7_1 test_primitive_xml_archive_dll: vc-7_1 test_primitive_xml_warchive: vc-7_1 test_primitive_xml_warchive_dll: vc-7_1 test_recursion_binary_archive: vc-7_1 test_recursion_binary_archive_dll: vc-7_1 test_recursion_text_archive: vc-7_1 test_recursion_text_archive_dll: vc-7_1 test_recursion_text_warchive: vc-7_1 test_recursion_text_warchive_dll: vc-6_5 vc-7_1 test_recursion_xml_archive: vc-7_1 test_recursion_xml_archive_dll: vc-7_1 test_recursion_xml_warchive: vc-7_1 test_recursion_xml_warchive_dll: vc-6_5 vc-7_1 test_registered_binary_archive: vc-7_1 test_registered_binary_archive_dll: vc-7_1 test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_registered_text_warchive: vc-7_1 test_registered_text_warchive_dll: vc-6_5 vc-7_1 test_registered_xml_archive: vc-7_1 test_registered_xml_archive_dll: vc-7_1 test_registered_xml_warchive: vc-7_1 test_registered_xml_warchive_dll: vc-6_5 vc-7_1 test_set_binary_archive: vc-7_1 test_set_binary_archive_dll: vc-7_1 test_set_text_archive: vc-7_1 test_set_text_archive_dll: vc-7_1 test_set_text_warchive: vc-7_1 test_set_text_warchive_dll: vc-7_1 test_set_xml_archive: vc-7_1 test_set_xml_archive_dll: vc-7_1 test_set_xml_warchive: vc-7_1 test_set_xml_warchive_dll: vc-7_1 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport vc-7_1 test_shared_ptr_132_binary_archive_dll: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport vc-7_1 test_shared_ptr_132_text_archive_dll: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport vc-7_1 test_shared_ptr_132_text_warchive_dll: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport vc-7_1 test_shared_ptr_132_xml_archive_dll: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport vc-7_1 test_shared_ptr_132_xml_warchive_dll: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 vc-7_1 test_shared_ptr_xml_warchive_dll: borland-5_6_4 intel-win32-8_1 vc-6_5 vc-7_1 test_simple_class_binary_archive: vc-7_1 test_simple_class_binary_archive_dll: vc-7_1 test_simple_class_ptr_binary_archive: vc-7_1 test_simple_class_ptr_binary_archive_dll: vc-7_1 test_simple_class_ptr_text_archive: vc-7_1 test_simple_class_ptr_text_archive_dll: vc-7_1 test_simple_class_ptr_text_warchive: vc-7_1 test_simple_class_ptr_text_warchive_dll: vc-6_5 vc-7_1 test_simple_class_ptr_xml_archive: vc-7_1 test_simple_class_ptr_xml_archive_dll: vc-7_1 test_simple_class_ptr_xml_warchive: vc-7_1 test_simple_class_ptr_xml_warchive_dll: vc-6_5 vc-7_1 test_simple_class_text_archive: vc-7_1 test_simple_class_text_archive_dll: vc-7_1 test_simple_class_text_warchive: vc-7_1 test_simple_class_text_warchive_dll: vc-7_1 test_simple_class_xml_archive: vc-7_1 test_simple_class_xml_archive_dll: vc-7_1 test_simple_class_xml_warchive: vc-7_1 test_simple_class_xml_warchive_dll: vc-7_1 test_split_binary_archive: vc-7_1 test_split_binary_archive_dll: vc-7_1 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_split_text_warchive: vc-7_1 test_split_text_warchive_dll: vc-7_1 test_split_xml_archive: vc-7_1 test_split_xml_archive_dll: vc-7_1 test_split_xml_warchive: vc-7_1 test_split_xml_warchive_dll: vc-7_1 test_tracking_binary_archive: vc-7_1 test_tracking_binary_archive_dll: vc-7_1 test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_tracking_text_warchive: vc-7_1 test_tracking_text_warchive_dll: vc-6_5 vc-7_1 test_tracking_xml_archive: vc-7_1 test_tracking_xml_archive_dll: vc-7_1 test_tracking_xml_warchive: vc-7_1 test_tracking_xml_warchive_dll: vc-6_5 vc-7_1 test_unregistered_binary_archive: vc-7_1 test_unregistered_binary_archive_dll: vc-7_1 test_unregistered_text_archive: vc-7_1 test_unregistered_text_archive_dll: vc-7_1 test_unregistered_text_warchive: vc-7_1 test_unregistered_text_warchive_dll: vc-6_5 vc-7_1 test_unregistered_xml_archive: vc-7_1 test_unregistered_xml_archive_dll: vc-7_1 test_unregistered_xml_warchive: vc-7_1 test_unregistered_xml_warchive_dll: vc-6_5 vc-7_1 test_variant_binary_archive: vc-7_1 test_variant_binary_archive_dll: vc-7_1 test_variant_text_archive: vc-7_1 test_variant_text_archive_dll: vc-7_1 test_variant_text_warchive: vc-7_1 test_variant_text_warchive_dll: vc-7_1 test_variant_xml_archive: vc-7_1 test_variant_xml_archive_dll: vc-7_1 test_variant_xml_warchive: vc-7_1 test_variant_xml_warchive_dll: vc-7_1 test_vector_binary_archive: vc-7_1 test_vector_binary_archive_dll: vc-7_1 test_vector_text_archive: vc-7_1 test_vector_text_archive_dll: vc-7_1 test_vector_text_warchive: vc-7_1 test_vector_text_warchive_dll: vc-7_1 test_vector_xml_archive: vc-7_1 test_vector_xml_archive_dll: vc-7_1 test_vector_xml_warchive: vc-7_1 test_vector_xml_warchive_dll: vc-7_1 |thread| test_barrier_lib: intel-9.0-linux test_condition_lib: intel-9.0-linux test_mutex_lib: intel-9.0-linux test_once_lib: intel-9.0-linux test_read_write_mutex_lib: intel-9.0-linux test_thread_lib: intel-9.0-linux test_tss_lib: intel-9.0-linux test_xtime_lib: intel-9.0-linux |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: intel-9.0-linux

1 0

[Review] Xpressive
by Fred 13 Sep '05

13 Sep '05

* What is your evaluation of the design? * What is your evaluation of the implementation? It's an extremely interesting library, and I really liked many of the design decisions made. I tried converting a simple Spirit grammar into an xpressive regex. I'll admit that this isn't a good idea, at least in my case, but it was an entertaining test of the library. The library seemed to do very well at most things I threw at it. I did run into one or two bugs, but Eric has already fixed them. MSVC7.1 frequently generated internal compiler errors, but the regex I was creating is hopefully significantly more complex than a regex should be. (I didn't profile it, but it looked as though it would be extremely slow as a regex.) One thing that I'd like to see improved is the ability to organize complex regexes. I think one example that I hope is easy to implement would be an ability to name a set of characters. There are a number of literals (_d, _w, etc.) that already do this. I would have found it useful to be able to name my own character sets in static regexes. * What is your evaluation of the documentation? Overall, it was extremely helpful. I did have a few minor complaints that I'll detail below: The syntax cheat sheet should have a string literal added to it. I'd like to see it be complete, and this is the only thing I could find that wasn't there. In addition, I'd like to be able to define character sets of my own that could be used in multiple places in my static regex. I'd like the documentation to better describe the _w identifier. I couldn't find the definition of word character. (I can imagine only one definition making sense, but that's not the same as having a definition.) On the page grammars_and_nested_matches.html, there is a discussion of how the library nicely handles all sorts different lifetime scenarios, but it does not discuss the lifetime of the regex refered to by a regex object that is refered to only through a by_ref clause in another regex. Does by_ref copy the object and manage the lifetime or not? One big advantage of static xpressive regexes is the potential of making a complex regex relatively readable. I'd like to see some discussion of this in the docs. (Something along the lines of http://www.boost.org/libs/spirit/doc/style_guide.html) The documentation of ~as_xpr( character_constant ) should be included. This is a useful construct. * What is your evaluation of the potential usefulness of the library? This will be an extremely useful library. I can see three reasons why this would be valuable to a user: It gives users another set of options to look at when trying to improve the performance of a regex. It makes it possible to create some fairly complex regexes that would be impossible or unreadable with the current boost regex library. The ability to refer to subexpressions in a static regex allows you to make a regex significantly easier to read and understand. Static regexes may be easier to read and understand than traditional string based regex languages, but I don't have enough experience to be confident of that statement. * Did you try to use the library? With what compiler? Did you have any problems? I played with it a bit. (See above.) I used MSVC7.1 and had slight troubles. (I also broke my personal record for long error messages. Even Spirit has never generated a 10MB error message for me before!) * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I read the documentation reasonably carefully and spent an afternoon writing some code with it. I did not test the code carefully, but I did get it to compile. * Are you knowledgeable about the problem domain? I've used boost::regex a fair amount. I've also used Spirit occasionally. * 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. Yes.

2 1

[Concepts] stl_concept_covering test
by Doug Gregor 13 Sep '05

13 Sep '05

This test is failing on a whole lot of compilers. For instance, see: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/ developer/issues.html Actually, a quick review shows that it fails on every compiler out there :) Normally, I'd blame the test itself, but given that this test was meticulously crafted to poke at the corner cases of STL implementations, it's very likely that the test is correct. Would someone volunteer to check out the errors and mark failures in explicit-failures-markup.xml appropriately? Doug

3 2