- Boost - lists.boost.org

[Boost-bugs] [ boost-Bugs-1338178 ] warning caused by size_t to unsigned int conversion on vc++8
by SourceForge.net 26 Oct '05

26 Oct '05

Bugs item #1338178, was opened at 2005-10-26 01:10 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=1338178&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: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: warning caused by size_t to unsigned int conversion on vc++8 Initial Comment: This is in collections_save_imp.hpp, line 36: unsigned int count = s.size(); I get a warning under vc++8: c:\boost\include\boost-1_33\boost\serialization\collections_save_imp.hpp(36) : warning C4267: 'initializing' : conversion from 'size_t' to 'unsigned int', possible loss of data I don't know if this is a foolish warning or not, or if changing to size_t would be detrimental to other platforms, but I thought I'd point it out just in case. bhiggins(a)gmail.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1338178&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Is there any interest in a library that provides containers with virtual destructors?
by Andy Tompkins 26 Oct '05

26 Oct '05

I have read a few times that people sometimes wish that std::vector (or other containers) had a virtual destructor. I have recently wished for the same thing and I fairly quickly write a class called virtual_vector something like: template <class Type, class Allo = std::allocator<Type> > class virtual_vector { public: ~virtual_vector(); ... private: std::vector<Type, Alloc> m_vector; }; All the public methods of std::vector are present in virtual_vector and are just forwarded on m_vector. This allows one to write something like: struct person { string first_name; string last_name; }; class people : public virtual_vector<person> { public: //extra methods }; Is this useful? Has this been done already? Thanks in advance for any comments? Andy Tompkins

2 1

Boost regression notification (2005-10-25 [RC_1_33_0])
by Douglas Gregor 25 Oct '05

25 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-25T14:49:08Z 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… 58 failures in 3 libraries: parameter (2) range (3) serialization (53) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_class_info_load_binary_archive: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos mingw-3_4_2 test_class_info_load_binary_archive_dll: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos intel-win32-8_1 mingw-3_4_2 test_class_info_load_text_archive: cw-9_4 gcc-3_4_3-sunos mingw-3_4_2 test_class_info_load_text_archive_dll: cw-9_4 gcc-3_4_3-sunos intel-win32-8_1 mingw-3_4_2 test_class_info_load_text_warchive: cw-9_4 gcc-3_4_3-sunos test_class_info_load_text_warchive_dll: cw-9_4 gcc-3_4_3-sunos intel-win32-8_1 test_class_info_load_xml_archive: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos mingw-3_4_2 test_class_info_load_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos intel-win32-8_1 mingw-3_4_2 test_class_info_load_xml_warchive: cw-9_4 gcc-3_4_3-sunos test_class_info_load_xml_warchive_dll: cw-9_4 gcc-3_4_3-sunos intel-win32-8_1 test_demo_xml_load: gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 mingw-3_4_2 test_demo_xml_load_dll: gcc-3_4_3-sunos gcc-4_0-darwin mingw-3_4_2 test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4

4 5

[Boost-bugs] [ boost-Support Requests-1337851 ] unknown compiler version
by SourceForge.net 25 Oct '05

25 Oct '05

Support Requests item #1337851, was opened at 2005-10-25 16:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1337851&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: Building Boost Group: None Status: Open Resolution: None Priority: 5 Submitted By: dstjames (dstjames) Assigned to: Nobody/Anonymous (nobody) Summary: unknown compiler version Initial Comment: I am not a developer but I need the boost librarys to compile a program I want to look at. When I try to install the boost library for GCC version 4.0.2_20050901-3 on SUSE 10.0 I get into an infinate loop where it keeps telling me unknown compiler version over and over. I am using the command bjam "-sTOOLS=gcc" install. Anyone know what this error means or a workaround? Thanks for any help. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1337851&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

boost::bind trouble
by Neal Becker 25 Oct '05

25 Oct '05

I'm using bind with boost-1.33. I can't get a simple test to work: ----------- #include <boost/bind.hpp> int G (int a, int b, int c) { return a + b + c; } int main () { int x = boost::bind (G,_1, 4, 8)(2); } ----------- g++ -fsyntax-only -I../ -I../../src TestScale.cc TestScale.cc: In function ‘int main()’: TestScale.cc:14: error: no match for call to ‘(boost::_bi::bind_t<int, int (*)(int, int, int), boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> > >) (int)’ /usr/include/boost/bind/bind_template.hpp:17: note: candidates are: typename boost::_bi::result_traits<R, F>::type boost::_bi::bind_t<R, F, L>::operator()() [with R = int, F = int (*)(int, int, int), L = boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> >] /usr/include/boost/bind/bind_template.hpp:23: note: typename boost::_bi::result_traits<R, F>::type boost::_bi::bind_t<R, F, L>::operator()() const [with R = int, F = int (*)(int, int, int), L = boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> >] /usr/include/boost/bind/bind_template.hpp:29: note: typename boost::_bi::result_traits<R, F>::type boost::_bi::bind_t<R, F, L>::operator()(A1&) [with A1 = int, R = int, F = int (*)(int, int, int), L = boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> >] /usr/include/boost/bind/bind_template.hpp:35: note: typename boost::_bi::result_traits<R, F>::type boost::_bi::bind_t<R, F, L>::operator()(A1&) const [with A1 = int, R = int, F = int (*)(int, int, int), L = boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> >]

3 3

FW: [Xpressive] quantify embedded regex - still no joy
by BRIDGES Dick 25 Oct '05

25 Oct '05

<update> The preprocessed source zip was too big so I removed it and am re-sending. I can e-mail the file if it would be useful. I ran the softfloat ARM cross-comiler against the exemplar and it compiled. Problem seems to be the x86 gcc 3.4.2 compiler? </update> -----Original Message----- From: BRIDGES Dick Sent: Tuesday, October 25, 2005 9:13 AM To: 'boost(a)lists.boost.org' Subject: RE: [boost] [Xpressive] quantify embedded regex - still no joy > -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Eric Niebler > Sent: Monday, October 24, 2005 4:56 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] [Xpressive] How to quantify embedded regex? > > > BRIDGES Dick wrote: > > I am trying to use Xpressive for parsing string-based > message buffers. > > The messages start with a fixed string and end with an "empty" line > > (similar in form to HTTP). Here is code that illustrates > my problem: > > > <snip> > > You're doing it right, and the commented out lines compile > for me (with > VC++ 7.1). I recently fixed a few bugs in this area, so perhaps you > could give the latest version (0.9.8a from Oct 19) a shot and let me > know if that works. <snip> > -- > Eric Niebler > Boost Consulting > www.boost-consulting.com I cleaned out the old version then installed 0.9.8a but I still get the same error on the same line: sregex re_ = "FROGGIE" >> _ln >> +(name_value_pair_) >> _ln; I'm going to try cross-compiling (the *real* target) this exemplar but that will take me a while to set up. In the meantime the error text and preprocessed source (zipped) from the most recent attempt are attached. I certainly appreciate your help with this. Regards, Dick Bridges

2 1

Boost regression notification (2005-10-25 [HEAD])
by Douglas Gregor 25 Oct '05

25 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-25T05:00:11Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 473 failures in 13 libraries: concept_check (13) date_time (2) graph (2) mpl (1) parameter (3) python (1) serialization (36) spirit (10) thread (4) tuple (1) type_traits (371) typeof (21) xpressive (8) |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 mingw-3_4_2 msvc vc-7_1 |date_time| testwcustom_time_zone: gcc-2.95.3-linux testwposix_time_zone: gcc-2.95.3-linux |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc tutorial: gcc-2.95.3-linux |python| exec: intel-win32-9_0 |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 test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |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 select_p_with_rule_debug: vc-7_1 switch_problem_debug: gcc-3_4_3-sunos vc-7_1 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 |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: 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 intel-win32-9_0 vc-7_1 tr1_add_cv_test: 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 intel-win32-9_0 vc-7_1 tr1_add_pointer_test: 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 intel-win32-9_0 vc-7_1 tr1_add_reference_test: 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 intel-win32-9_0 vc-7_1 tr1_add_volatile_test: 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 intel-win32-9_0 vc-7_1 tr1_aligned_storage_test: 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 intel-win32-9_0 vc-7_1 tr1_alignment_of_test: 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 intel-win32-9_0 vc-7_1 tr1_extent_test: 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 intel-win32-9_0 vc-7_1 tr1_has_nothrow_assign_test: 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 intel-win32-9_0 vc-7_1 tr1_has_nothrow_constr_test: 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 intel-win32-9_0 vc-7_1 tr1_has_nothrow_copy_test: 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 intel-win32-9_0 vc-7_1 tr1_has_trivial_assign_test: 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 intel-win32-9_0 vc-7_1 tr1_has_trivial_constr_test: 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 intel-win32-9_0 vc-7_1 tr1_has_trivial_copy_test: 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 intel-win32-9_0 vc-7_1 tr1_has_trivial_destructor_test: 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 intel-win32-9_0 vc-7_1 tr1_has_virtual_destructor_test: 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 intel-win32-9_0 vc-7_1 tr1_is_abstract_test: 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 intel-win32-9_0 vc-7_1 tr1_is_arithmetic_test: 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 intel-win32-9_0 vc-7_1 tr1_is_array_test: 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 intel-win32-9_0 vc-7_1 tr1_is_base_of_test: 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 intel-win32-9_0 vc-7_1 tr1_is_class_test: 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 intel-win32-9_0 vc-7_1 tr1_is_compound_test: 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 intel-win32-9_0 vc-7_1 tr1_is_const_test: 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 intel-win32-9_0 vc-7_1 tr1_is_convertible_test: 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 intel-win32-9_0 vc-7_1 tr1_is_empty_test: 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 intel-win32-9_0 vc-7_1 tr1_is_enum_test: 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 intel-win32-9_0 vc-7_1 tr1_is_floating_point_test: 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 intel-win32-9_0 vc-7_1 tr1_is_function_test: 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 intel-win32-9_0 vc-7_1 tr1_is_fundamental_test: 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 intel-win32-9_0 vc-7_1 tr1_is_integral_test: 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 intel-win32-9_0 vc-7_1 tr1_is_member_func_test: 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 intel-win32-9_0 vc-7_1 tr1_is_member_obj_test: 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 intel-win32-9_0 vc-7_1 tr1_is_member_pointer_test: 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 intel-win32-9_0 vc-7_1 tr1_is_object_test: 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 intel-win32-9_0 vc-7_1 tr1_is_pod_test: 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 intel-win32-9_0 vc-7_1 tr1_is_pointer_test: 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 intel-win32-9_0 vc-7_1 tr1_is_polymorphic_test: 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 intel-win32-9_0 vc-7_1 tr1_is_reference_test: 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 intel-win32-9_0 vc-7_1 tr1_is_same_test: 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 intel-win32-9_0 vc-7_1 tr1_is_scalar_test: 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 intel-win32-9_0 vc-7_1 tr1_is_signed_test: 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 intel-win32-9_0 vc-7_1 tr1_is_union_test: 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 intel-win32-9_0 vc-7_1 tr1_is_unsigned_test: 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 intel-win32-9_0 vc-7_1 tr1_is_void_test: 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 intel-win32-9_0 vc-7_1 tr1_is_volatile_test: 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 intel-win32-9_0 vc-7_1 tr1_rank_test: 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 intel-win32-9_0 vc-7_1 tr1_remove_all_extents_test: 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 intel-win32-9_0 vc-7_1 tr1_remove_const_test: 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 intel-win32-9_0 vc-7_1 tr1_remove_cv_test: 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 intel-win32-9_0 vc-7_1 tr1_remove_extent_test: 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 intel-win32-9_0 vc-7_1 tr1_remove_pointer_test: 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 intel-win32-9_0 vc-7_1 tr1_remove_reference_test: 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 intel-win32-9_0 vc-7_1 tr1_remove_volatile_test: 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 intel-win32-9_0 vc-7_1 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc 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 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[Boost-bugs] [ boost-Bugs-1337412 ] Compiler warning with gcc on Linux
by SourceForge.net 25 Oct '05

25 Oct '05

Bugs item #1337412, was opened at 2005-10-25 05:52 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=1337412&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: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: Compiler warning with gcc on Linux Initial Comment: I get the following warning compiling on Linux with gcc. No mater what I do I can't seem to get around the warning. Any ideas? Thanks! g++ -c -pipe -Wall -W -g -fPIC -I/usr/lib/qt-3.1/mkspecs/default -I. -I. -Iinclude -Isrc -I../ccbus -I/usr/lib/qt-3.1/include -I.ui/ -I.moc/ -o .obj/TraderButtonKey.o src/TraderButtonKey.cpp /usr/include/boost/archive/detail/common_iarchive.hpp: In member function `void boost::archive::detail::common_iarchive<Archive>::init() [with Archive = boost::archive::text_iarchive]': /usr/include/boost/archive/text_iarchive.hpp:69: instantiated from `boost::archive::text_iarchive_impl<Archive>::text_iarchive_impl(std::istream&, unsigned int) [with Archive = boost::archive::text_iarchive]' /usr/include/boost/archive/text_iarchive.hpp:82: instantiated from here /usr/include/boost/archive/detail/common_iarchive.hpp:75: warning: choosing ` boost::archive::version_type::operator unsigned int&()' over ` boost::archive::version_type::operator unsigned int() const' /usr/include/boost/archive/detail/common_iarchive.hpp:75: warning: for conversion from `boost::archive::version_type' to `unsigned int' /usr/include/boost/archive/detail/common_iarchive.hpp:75: warning: because conversion sequence for the argument is better Code fragment: class TraderButtonKey { public: //! Default constructor. TraderButtonKey( ) : m_cls(0), m_number(0) {} //! Constructor. //! //! \param cls the class //! \param number the number TraderButtonKey( int cls, int number ) : m_cls(cls), m_number(number) {} ... private: //! Required by the boost C++ libraries to provide serialization to //! and from the archive. //! //! \param ar archive to save/load object members //! \param version boost class version template<class Archive> void serialize( Archive & ar, const unsigned int version ) { if (version) // gets rid of unused parameter warning ; ar & m_cls; ar & m_number; } int m_cls; //!< class of the key int m_number; //!< number within that class }; ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1337412&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Xpressive] How to quantify embedded regex?
by BRIDGES Dick 24 Oct '05

24 Oct '05

I am trying to use Xpressive for parsing string-based message buffers. The messages start with a fixed string and end with an "empty" line (similar in form to HTTP). Here is code that illustrates my problem: int main(int argc, char **argv) { std::string buffer_ = "FROGGIE\r\n" "Volume = 3\r\n" "Other1= 0\r\n" "Channel=1\r\n" "Other =2\r\n" "\r\n" "FROGGIE\r\n" "Volume = 4\r\n" "Other1= 8\r\n" "Channel=5\r\n" "Other =3\r\n" "\r\n" "FROGGIE\r\n" "Volume = 4\r\n" "Other1= 8\r\n" "Channel=5\r\n"; // mark_tag name_(1), value_(2); To be used in the name_value_pair later. sregex name_value_pair_ = +alnum >> *_s >> "=" >> *_s >> +_d >> *_s >> _ln; sregex re_ = "FROGGIE" >> _ln >> name_value_pair_ >> _ln; // sregex re_ = "FROGGIE" >> _ln >> repeat<1,5>(name_value_pair_) >> _ln; // sregex re_ = "FROGGIE" >> _ln >> +(name_value_pair_) >> _ln; } The only examples of repeating an embedded regex I could find in the .pdf or the examples subdirectory used predefined regexes like alnum but still, it looked to me that the lines that are commented out should have worked. I am clearly wrong. Both of these forms create very long error messages that end with "internal compiler error". One of those error messages is included as an attachment. The uncommented line compiles fine. Since I'm not very accomplished at regular expressions, maybe I should point out that, besides being able to extract the name/value pairs from each message in turn, I want to use what.suffix() to identify the partial message at the end of the buffer. OS is Linux Core 3 2.6.9-1.667. Compiler is gcc 3.4.2 20041017 (Red Hat 3.4.2-6fc5). Xpressive README (in the .zip) says "Last Modified: October 9, 2005". If someone could point me in the right direction, I'd surely appreciate it. If this query is not appropriate for this group, should I post it to boost-users(a)lists.boost.org or mail the author directly or..? Regards, Dick Bridges

2 1

Re: [boost] boost::dynamic_array
by Martin Bonner 24 Oct '05

24 Oct '05

----Original Message---- From: Boris [mailto:boris@gtemail.net] Sent: 04 October 2005 13:18 To: boost(a)lists.boost.org Subject: Re: [boost] boost::dynamic_array > The reason why I don't want to use std::vector in the project I work > on is that I need a two-dimensional array. Two-dimensional means that > the array stores not only the length but also width and height. > Additionally its elements can be accessed with operator()(size_t > column, size_t row). Now I could derive my two-dimensional array from > std::vector but that doesn't make much sense because how should the > dimensions change when someone calls push_back()? A fixed-size array > whose size can be set a runtime would be an ideal candidate to derive > my two-dimensional array from. For all arrays with more than one > dimension std::vector isn't probably an ideal parent class. So don't /derive/ from std::vector, /contain/ a std::vector instead (and forward the appropriate calls to it). It's really not very difficult (particularly as you don't need to both with eg any of the 'insert' overloads). -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 2