- Boost - lists.boost.org

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

17 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-16T14:08: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… 3 failures in 3 libraries: multi_index (1) serialization (1) thread (1) |multi_index| test_conv_iterators: vc-8_0 |serialization| test_multiple_ptrs_binary_archive: vc-8_0 |thread| test_mutex_lib: tru64cxx71-006

3 2

[Boost-bugs] [ boost-Support Requests-1358740 ] boost_1_33_0 regex runtime assertion fail.
by SourceForge.net 17 Nov '05

17 Nov '05

Support Requests item #1358740, was opened at 2005-11-17 07:24 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=1358740&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: mindaou (mindaou) Assigned to: Nobody/Anonymous (nobody) Summary: boost_1_33_0 regex runtime assertion fail. Initial Comment: Hi, I am new in boost. I use boost_1_33_0 and VC7.1. When I run the regex sample code(string split and credit card number check), assertion failed. I dont know how to solve it. I build and install boost like this: bjam "-sTOOLS=vc-7_1" install Then I set the include path and library path in VC7.1. I can compile and build(debug mode) the program successfully, but fail to execute it. The assertion fail message is as following: Assertion failed: r == 1 << 8, file C:\boost_1_33_0\libs\regex\build\../src/w32_ regex_traits.cpp, line 108 ------ Then I tried using another boost library "tokenizer". It works good. I think I install boost properly. I just can't figure out why I can't use regex. My VC7.1 environment settings are all default. I tried another VC6-built boost, and it has the same assertion fail with my VC6. Can anyone help me with this? Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1358740&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. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Bugs-1358600 ] lexical_cast & pure virtual functions & VC 8 STL
by SourceForge.net 17 Nov '05

17 Nov '05

Bugs item #1358600, was opened at 2005-11-17 11:39 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=1358600&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sergey Shandar (sergey_shandar) Assigned to: Nobody/Anonymous (nobody) Summary: lexical_cast & pure virtual functions & VC 8 STL Initial Comment: VC 8.0 can't compile the valid code: ===== ===== #include <boost/lexical_cast.hpp> class A { public: virtual void out(std::ostream &) const = 0; }; class B: public A { public: virtual void out(std::ostream &O) const { O << "B"; } }; std::ostream &operator<<(std::ostream &O, const A &a) { a.out(O); return O; }; int main() { const A &a = B(); boost::lexical_cast<std::string>(a); return 0; } ===== ===== The problem occurs in VC STL: ===== ===== c:\program files\microsoft visual studio 8\vc\include\limits(102) : error C2259: 'A' : cannot instantiate abstract class ===== ===== However, should boost::lexical_cast use std::numeric_cast in this case? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1358600&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. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] "Re: serialization performance"
by bwood 17 Nov '05

17 Nov '05

Caleb Epstein wrote: >On Tue, 15 Nov 2005 02:08:52 00100 (CET), bwood <brass_at_[hidden]> wrote: > > >> I'm not sure if I understand your first question. I assume >> you read the previous posts. I compared the time it takes to >> serialize/send a list of ints using Boost and Ebenezer approaches. >> I timed the following >> Boost: >> oArch & lst; // using boost 1.33.0 >> Ebenezer: >> msgs.Send(buffer, lst); >> >> >> Without making any modifications to the two "vanilla" approaches, >> Boost takes more than twice as long than Ebenezer. On the > > >Someone has proposed an enhancement for Serialization that would speed up >array/vector operations by an order of magnitude. I don't think such a >simple test is indicative of the overall performance or feature-set of >either of these two libraries. Perhaps Boost.Serialization does not >perform >well with a list of ints, but Ebenezer does. Maybe >Boost.Serializationperforms better with scalar values, or with tracked >objects, or with the XML >based archive, who knows. That enhancement sounds familiar. Is the aim to take advantage of the contiguous data? WebEbenezer already implements a limited form of this with arrays and vectors. Certainly Boost.Serialization is better with XML. We don't support XML and don't plan to. > >> It may be that gcc doesn't optimize the Boost code >> very well and another compiler would produce results that >> are better. > > >Who knows, but what you are benchmarking is far to small to be meaningful >IMHO. "A single accurate measurement is worth a thousand expert opinions." I hope to add to the tests over time and add a page to webEbenezer that will cover the results. > > >> As far as build times, I agree that they aren't the most >> important factor. In my opinion they aren't trivial either. > > >Features are much more important to me and I am sure many others. I have a >hard time believing that "Ebenezer" can compete with >Boost.Serializationwhich: > > > - Has an extensive unit-test suite and compiles on a broad range of > platforms/compilers We have a variety of tests. Our approach to serialization is different than the library approach. We don't need to port a library to different platforms/compilers. We don't use areas of C++ that are dark corners in terms of the code that is output, so I think it reasonable to believe we have a broader reach than Boost.Serialization in this respect. This is ironic as we don't have to work hard, like Boost does, to achieve this. > - Supports several different archive formats (e.g. text, binary, xml) > - Supports object versioning S11n.net, CORBA and webEbenezer don't find a place for "versioning." I think code like what you wrote when I asked about changing a member's type between releases should go into a utility program that gets run once. If you stick that code into an application it gets run over and over, but adds nothing as far as functionality. > - Supoprts pointer serialization/tracking We support pointer serialization but not tracking yet. > - Is not coupled to a transport (the Ebenezer example code I can see > seems very socket or file-centric) > True, but that could change if needed. Brian

1 0

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

16 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-16T06:00:27Z 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… 137 failures in 14 libraries: concept_check (12) date_time (2) graph (2) io (1) iostreams (2) iterator (2) math (5) mpl (1) serialization (30) spirit (2) tr1 (52) type_traits (3) typeof (18) xpressive (5) |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 vc-7_1 |date_time| testwcustom_time_zone: mingw-3_4_2 testwposix_time_zone: mingw-3_4_2 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |iostreams| auto_close_test: vc-7_1 finite_state_filter_test: vc-7_1 |iterator| iterator_traits_test: vc-7_1 permutation_iterator_test: vc-7_1 |math| complex_test: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos log1p_expm1_test: gcc-3_4_3-sunos |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| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux 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_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-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_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-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_has_virtual_destructor_test: gcc-3_4_3-sunos intel-win32-9_0 mingw-3_4_2 |type_traits| has_virtual_destructor_test: gcc-3_4_3-sunos intel-win32-9_0 mingw-3_4_2 |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

3 2

[website] broken links on version history page.
by Rene Rivera 16 Nov '05

16 Nov '05

An FYI... when the 1.33.0 changes got moved from the front page to the history page the links did not get adjusted so they now point to nothing. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

2 2

Some simple logging performance tests
by Andrew Schweitzer 16 Nov '05

16 Nov '05

Using GetTickCount and GetThreadTimes on Windows XP Pro, recorded time to execute some simple pieces of logging code in a loop. Divided by loop iterations to get time per iteration. This is a 3Ghz Pentium. Not sure how good these tests are, but here's the results: results: elapsed ms thread time ms ns / call (GetTickCount) (GetThreadTimes) (in thread) cout 1329 421 42100 enabled log 1469 453 45300 cout "disabled" 15 15 15 disabled log 531 531 531 Here's a little detail on tests cout, 10,000 times, l_dw increments each loop: cout << l_dw << endl; enabled log, 10,000 times: //outside loop: enable_logs("lgTest"); //in loop: BOOST_SCOPEDLOG(l_lgTest) << l_dw << endl; cout "disabled", 1,000,000 times: //outside loop: bool l_bEnabled = false; //in loop: if(l_bEnabled) { cout << l_dw << endl; } disabled log, 1,000,000 times: //outside loop: disable_logs("lgTest"); //this not in loop //in loop: BOOST_SCOPEDLOG(l_lgTest) << l_dw << endl;

6 9

[Review] The review of the Boost.Logging library starts today, November 7th
by Hartmut Kaiser 16 Nov '05

16 Nov '05

Hi all, today starts the review of the Boost.Logging library written by John Torjo. It will end on November 16th. --------------------------------------------------- About the library: As applications are becoming more and more complex, logging is more and more of a must, in nowadays software. The Boost Logging Library is a library that: * makes it very easy to declare/define logs * allows you very simple access to logs * allows you to easily use/manipulate log levels (like, dbg/err/info/etc.) * allows for log hierarchies, and for manipulating log hierarchies * is thread-safe To get you started, here's some basic usage: BOOST_LOGL(app,dbg) << "debugging: " << i << '-' << j << std::endl; BOOST_LOG(app) << "I just wanted to tell you something...."; BOOST_LOGL(app,err) << "this is an error!"; The latest version of the lib can be found here: http://torjo.com/code/logging.zip --------------------------------------------------- Please always state in your review, whether you think the library should be accepted as a Boost library! Additionally please consider giving feedback on the following general topics: - 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? Regards Hartmut Review Manager

14 46

mpl help needed - doing the impossible?
by Manfred Doudar 16 Nov '05

16 Nov '05

I'm Re-posting ... sorry for the noise, but this seemingly, earlier went against the unit lib thread .. (don't quite know how). Boosters: I'm hoping someone here might be of help, and enlighten me with some more MPL trickery ... What I'm doing: Have a class MyArray derived from blitz::Array, and among other things, I'm trying to add the operator[] to slice through a multi-dim array ... pretty much have it, with one exception - once I get to applying [] on a 1-dimensional (linear) array, I of course expect a scalar, but therein lies the problem - the compiler also "sees" a 0-dimensional array (not good!), and that's where I run into problems... Brief snippets of code: Please ignore the return by value for the moment - I can clean that up later, not to mention the Boost PP extensions I can add. Below is a cut-down class definition, and method implementation follows. Class Declaration: ------------------ template <typename T, int Rank = 1> class MyArray : public blitz::Array<T, boost::mpl::int_<Rank>::value> { public: // ... methods }; (Partial Listing) Implementation: --------------------------------- template <typename T, int Rank> MyArray<T, Rank> :: Array(const blitz::Array<T, boost::mpl::int_<Rank>::value>& btz ) throw() : blitz::Array<T, boost::mpl::int_<Rank>::value> (const_cast<T *> (btz.data()) , btz.shape() , blitz::duplicateData ) { // Copy Ctor } template <typename T, int Rank> void MyArray<T, Rank> :: getParamList(blitz::TinyVector< boost::variant< blitz::Range , blitz::nilArraySection > , 2 >& plist ) { // Aides us in setting up the parameter list for slicing plist(boost::mpl::int_<0>::value) = blitz::Range::all(); plist(boost::mpl::int_<1>::value) = blitz::nilArraySection(); } /* Now, how do I get T out when Rank == 1, ... compiler complains about seeing a MyArray/blitz::Array of <T, Rank = 0> (, which is not defined for blitz Arrays) */ template <typename T, int Rank> typename boost::mpl::if_ < typename boost::mpl::equal_to < boost::mpl::int_<Rank> , boost::mpl::int_<1> >::type , T , MyArray<T, boost::mpl::int_<Rank>::prior::value> >::type MyArray<T, Rank> :: operator[] (const int& index) throw(); { // Slicing // this bit of indirection is useful blitz::TinyVector<boost::variant<blitz::Range, blitz::nilArraySection>, 2> plist; this->getParamList(plist); /* pseudocode: (kind of) **************** return // cast for return type static_cast< (Rank == 1 ? T : MyArray<T, Rank - 1>) > ( // cast _this_ ptr * static_cast<const blitz::Array<T, Rank> *> (this) // the blitz Array parameter list (index, //the param list *boost::get<blitz::Range *or* blitz::nilArraySection>(&plist(0 *or* 1), ... ) ) Sample usage: MyArray<float, 3> arr(btzArray); arr[10]; // gives MyArray<float, 2> out arr[10][2] // gives MyArray<float, 1> out arr[10][2][7] // expect a float to be output ********************/ return static_cast< typename boost::mpl::if_< typename boost::mpl::equal_to< boost::mpl::int_<Rank> , boost::mpl::int_<1> >::type , T , MyArray<T, boost::mpl::int_<Rank>::prior::value> >::type > ((* static_cast<const blitz::Array<T, boost::mpl::int_<Rank>::value> *> (this)) /* the parameter list */ (index, *boost::get< typename boost::mpl::if_< typename boost::mpl::less< boost::mpl::int_<1> , boost::mpl::int_<Rank> >::type , blitz::Range , blitz::nilArraySection >::type > (&plist(boost::mpl::if_< typename boost::mpl::less< boost::mpl::int_<1> , boost::mpl::int_<Rank> >::type , boost::mpl::int_<0> , boost::mpl::int_<1> >::type::value ) ) /* , ... we can extend the parameter list with Boost.PP */ ); ************* (Partial) Compiler Error Messages: --------------------------------- `boost::mpl::algo_::if_<boost::mpl::equal_to<boost::mpl::int_<Rank>, boost::mpl::int_<1> >::type, T, blitz::Array<T, typename boost::mpl::int_<Rank>::prior::value> >::type moe::Array<T, Rank>::operator[](const S&) [with S = int, T = int, int Rank = 1]': arr.cc:172: instantiated from here arr.cc:666: invalid static_cast from type `blitz::Array<int, 0>' to type `int' /usr/local/include/blitz/array/storage.h: In constructor `blitz::GeneralArrayStorage<N_rank>::GeneralArrayStorage() [with int N_rank = 0]': <snip ... more messages> /usr/local/include/blitz/array/storage.h:60: no match for call to `( blitz::TinyVector<int, 0>) (int&)' <snip ... more messages> ******************* So ... can anyone tell me if what I'm trying to do is possible ? Is there some MPL trickery to do it ? The above does work up until I apply the operator[] on a 1-d linear array. Help and ideas would be appreciated. Ah yes, using gcc 3.2.2, and Boost version 1.31 (maybe 1.32) .. downloaded in August 2004 (yes, I know that's ancient - but managment can be a real pain sometimes) P.S. tried to format this message as best I could, hope it's readable. With Thanks, -- Manfred Doudar MetOcean Engineers www.metoceanengineers.com

1 0

Weak_ptr and operator==
by Dan Day 15 Nov '05

15 Nov '05

Why was operator== never added to weak_ptr? Couldn't the operator easily be implemented in terms of operator<? -- ------------------------------------------- Dan Day http://razzerblog.blogspot.com

3 2