- Boost - lists.boost.org

[Serialization] [1.33.1-beta] Does not compile with GCC 2.95.4
by Simon Barner 10 Nov '05

10 Nov '05

Hi, I tried to build boost 1.33.1 with gcc 2.95.4, using STL-port and Spirit 1.6.2. It worked quite well, but I had to comment out the following lines: --- boost/archive/detail/oserializer.hpp.orig Thu Nov 10 00:40:32 2005 +++ boost/archive/detail/oserializer.hpp Thu Nov 10 00:43:15 2005 @@ -330,9 +330,9 @@ { static const basic_pointer_oserializer * register_type(Archive & /* ar */){ // it has? to be polymorphic - BOOST_STATIC_ASSERT( - boost::serialization::type_info_implementation<T>::type::is_polymorphic::value - ); + //BOOST_STATIC_ASSERT( + //boost::serialization::type_info_implementation<T>::type::is_polymorphic::value + //); return static_cast<const basic_pointer_oserializer *>(NULL); } }; As far as I understand this will not affect the runtime behaviour, but it will disable some compile time assertation check. Perhaps you want to fix it. Please Cc: me in your replies, I am not on the list. -- Best regards / Viele Grüße, barner(a)FreeBSD.org Simon Barner barner(a)gmx.de

2 1

XML APIs: use cases, and wishes
by Andreas Pokorny 09 Nov '05

09 Nov '05

Hi there, Stefan Seefeld recently presented his set of Dom classes. Personally I do not have any need for a DOM API. To focus the discussion on other APIs I started this new thread (and also because I could not find a good entry point in the previous disucussions). Last time I had to process XML I wrote my own wrapper on top of SAX, which forwarded higher level events to xml-unaware structures. The model served well to directly map a fixed XML-format to C++ structures (also XML writing was supported). The wrapper that forwarded all SAX events to the datastructures was generated from a single C++ expression, or several if recursion was required. I adopted a lot of spirits techinques to make it look nice. There were no intermediate data structures. In retrospective I also dislike my attempt, although it was better than working on xml document classes. It only worked with full xml documents, no partial parsing was supported. Furthermore it required a nearly direct mapping of xml elements to datastructures, different use cases which do not include a mapping of xml<->c++ werent considered. I currently do not need to fiddle with XML, but I would like to see at least these different APIs: * on-demand parsing, a parser drived by a cursor, that allows to navigate through a document, without loading it completly (I dont see a need for prior validation, here) * xml path / query like api to fastly grep for certain subtrees or elements of the xml * direct mapper of c++ structures to a certain format, so a kind of xml serialization, As you can see my view on XML is very limited, it boils down to a flexilbe form of reading XML. Regards, Andreas Pokorny

6 7

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

09 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-09T13:48:12Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. utility Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 7 failures in 6 libraries: graph (2) random (1) regex (1) serialization (1) utility (1) wave (1) |graph| betweenness_centrality_test: vc-8_0 floyd_warshall_test: vc-8_0 |random| random_test: mingw-3_4_2 |regex| regex_regress_dll: vc-8_0 |serialization| test_exported_xml_warchive_dll: vc-8_0 |utility| operators_test: vc-8_0 |wave| testwave: mingw-3_4_2

1 0

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

09 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-09T06:00:59Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 191 failures in 12 libraries: bind (1) concept_check (10) graph (1) io (1) mpl (1) serialization (30) spirit (8) thread (4) tr1 (111) tuple (1) typeof (18) xpressive (5) |bind| bind_dm3_test: intel-win32-9_0 |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 |graph| layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_bind: gcc-2.95.3-linux intel-win32-9_0 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_bind: intel-win32-9_0 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_bounds_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux tr1_tricky_abstract_type_test: gcc-2.95.3-linux tr1_tricky_add_pointer_test: gcc-2.95.3-linux tr1_tricky_incomplete_type_test: gcc-2.95.3-linux tr1_tricky_partial_spec_test: gcc-2.95.3-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

threads - suggestion for producer/consumer pattern - synchronisation channel
by Oliver.Kowalke＠infineon.com 09 Nov '05

09 Nov '05

Hello, I've a suggestion for an implementation of the synchronization channel between producer and consumer threads. It is adopted from several books - the only problem is how to tell the consumer threads, that all producer have finished their jobs. You can signal it from outside (deactive member function) or each producer thread has to register on the message_queue (and unregister if it has finished its job). With best regards, Oliver <<test.cpp>> <<message_queue.h>>

2 1

How to contact with Review Wizard?
by Alexander Nasonov 09 Nov '05

09 Nov '05

I wrote two letters to Tom Brinkman from different e-mail addresses but has no reply. -- Alexander

2 2

[Boost-bugs] [ boost-Bugs-1352049 ] EdgeListS = has_setS for adjacency_list does not work
by SourceForge.net 09 Nov '05

09 Nov '05

Bugs item #1352049, was opened at 2005-11-09 02:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1352049&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: graph Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Jeremy Siek (jsiek) Summary: EdgeListS = has_setS for adjacency_list does not work Initial Comment: hash_set header isn't in #include <hash_set> for every compilers. Example to include the correct header for gcc: # if defined __cplusplus # if defined __GNUC__ && __GNUC__ >= 3 # include <ext/hash_set> # if __GNUC__ >= 4 || __GNUC_MINOR__ >= 2 namespace std { using ::__gnu_cxx::hash; using ::__gnu_cxx::hash_set; } # endif # else # include <hash_set> # endif /* defined __GNUC__ and __GNUC__ == 3 */ # endif /* defined __cplusplus */ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1352049&group_… ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] Gender neutral documentation
by Martin Bonner 09 Nov '05

09 Nov '05

----Original Message---- From: brangdon(a)cix.compulink.co.uk [mailto:brangdon@cix.compulink.co.uk] Sent: 08 November 2005 21:58 To: boost(a)lists.boost.org Subject: Re: [boost] Gender neutral documentation > In-Reply-To: <dkl36d$2ak$1(a)sea.gmane.org> > andy(a)servocomm.freeserve.co.uk (Andy Little) wrote (abridged): >> Where it is used 'she' always refers to 'the user'. > > If you have two protagonists (author and user) it can help to give > them different genders and to be consistent about which way round > they are. > > >> I dont use that convention myself for obvious reasons ! > > Hmm. I suspect we could argue about this for weeks. > Weeks? I would have said that was out by about two orders of magnitude :-) My prediction is that a consensus will emerge on how to handle this across the English speaking(writing) world - by about the middle of this century. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

linker problem ob HP/UX - wrong extension
by Oliver.Kowalke＠infineon.com 09 Nov '05

09 Nov '05

Hello, I compiled boost on HP/UX 11.11 (PA RISC) with gcc. I got a linker error if I tried to link against the regex library: /usr/ccs/bin/ld: Invalid loader fixup in text space needed in output file for symbol "__gxx_personality_sj0" in input file "/opt/boost/lib/libboost_regex-gcc." What I found out was: 1) 'bjam "-sTOOLS=gcc" install' creates libraries with wrong extension (*.so instead of *.sl) /opt/boost/lib/libboost_regex-gcc.a /opt/boost/lib/libboost_regex-gcc.so 2) It seams that the linker chooses the static library if I declare '- boost_regex-gcc', so I get the linker error as described in my prevoíous email! 3) Building boost with 'bjam "-sSUFDLL=.sl" "-sTOOLS=gcc" install' creates /usr/local/lib/libboost_regex-gcc-1_33.a /usr/local/lib/libboost_regex-gcc-1_33.s /usr/local/lib/libboost_regex-gcc.a Shared library /usr/local/lib/libboost_regex-gcc.sl is missing! 4) Now linking with '- boost_regex-gcc-1_33' works (no linker error). Conclusion: 1) The extension for HP/UX libraries should be fixed. 2) The shared library without version in its name is missing. So long, Oliver

1 0

Re: [boost] Gender neutral documentation
by brangdon＠cix.compulink.co.uk 08 Nov '05

08 Nov '05

In-Reply-To: <u1x1ua1zr.fsf(a)boost-consulting.com> dave(a)boost-consulting.com (David Abrahams) wrote (abridged): > >> For example, if Bind is unneeded the user can discard it > >> completely. > >> > >> is much more to the point. > > > > But "is unneeded" again fails to say who doesn't need it, and hence > > fails to say why it isn't needed. > > I don't see how saying who doesn't need it would indicate anything > about why it isn't needed. If it is you who needs it, you also know why you need it. If it is the library which sometimes needs it, you have to guess when. -- Dave Harris, Nottingham, UK.

1 0