- Boost - lists.boost.org

[interprocess] difference between resize & reserve
by Dmitry Smirnov 14 Aug '06

14 Aug '06

Hi, Ion! It seems I found the difference between "resize" and "reserve" After changing resize to reserve in following code m_objSendVectorStream.tellp() will return -1 instead of size of data packet :-( m_objSendVectorStream.resize( QueueSettings::maxMessageSize() ); m_objSendVectorStream.seekp( 0 ); { boost::archive::defOArchive objOArchive( m_objSendVectorStream ); objOArchive << objData; }

2 2

[defer/thread_pool] - added again to boost vault
by Oliver.Kowalke＠qimonda.com 14 Aug '06

14 Aug '06

Hello, because on the user list a library which allows reuse of threads was requested I've added the defer library, originally developed by Simon Meiklejohn, to the boost vault (concurrent programming - I don't know why it was removed?). I've modified the library a little bit - a threaded queue for the thread pool was added. Maybe we can discuss the solution?! regards, Oliver

3 2

bugs in 1-33-1 iostreams non_blocking_adapter.hpp
by George M. Garner Jr. 13 Aug '06

13 Aug '06

Today I ran into two bugs in non_blocking_adapter.hpp. The code quoted below results for both read() and write() results in an endless loop if iostreams::read() or iostreams::write(), respectively, returns 0. Also, since std::streamsize is an integer, the code in both places should check for amt < 0. The correct algorithm in both cases is: if(amt <= 0) break Regards, George. starting line 26: std::streamsize read(char_type* s, std::streamsize n) { std::streamsize result = 0; while (result < n) { std::streamsize amt = iostreams::read(device_, s, n); if (amt == -1) break; result += amt; //<-- infinite loop if amt == 0 } return result != 0 ? result : -1; } std::streamsize write(const char_type* s, std::streamsize n) { std::streamsize result = 0; while (result < n) { std::streamsize amt = iostreams::write(device_, s + result, n - result); result += amt; // <-- infinite loop if amt == 0 } return result; }

1 0

Boost regression notification (2006-08-12 [RC_1_34_0])
by Douglas Gregor 12 Aug '06

12 Aug '06

Boost Regression test failures Report time: 2006-08-12T10:38:51Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 204 failures in 24 libraries algorithm/string (1) concept_check (1) filesystem (4) graph (5) io (1) iostreams (10) mpl (6) numeric/conversion (4) numeric/interval (1) numeric/ublas (7) parameter (20) program_options (9) python (21) random (1) rational (4) regex (1) serialization (26) signals (16) spirit (1) test (2) tr1 (51) typeof (8) utility (1) wave (3) |algorithm/string| regex: borland-5_6_4 |concept_check| class_concept_check_test: vc-7_1-stlport |filesystem| mbcopy: sun-5.8 operations_test: vc-7_1-stlport operations_test_dll: vc-7_1-stlport wide_test: sun-5.8 |graph| adjacency_matrix_test: vc-7_0 csr_graph_test: sun-5.8 graphviz_test: msvc-8.0 msvc-8.0 vc-7_1-stlport |io| ios_state_unit_test: gcc-4.1.0_linux_x86_64 |iostreams| bzip2_test: msvc-7.1 msvc-8.0 compose_test: borland-5_6_4 example_test: vc-6_5-stlport filtering_stream_test: vc-7_1-stlport finite_state_filter_test: cw-9.4 gzip_test: msvc-7.1 msvc-8.0 zlib_test: msvc-7.1 msvc-8.0 |mpl| multiset: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 vector_c: sun-5.8 |numeric/conversion| converter_test: borland-5_8_2 traits_test: borland-5_8_2 udt_example_0: borland-5_8_2 udt_support_test: borland-5_8_2 |numeric/interval| test_float: vc-7_1-stlport |numeric/ublas| concepts: vc-7_1-stlport vc-7_1-stlport test1: vc-7_1-stlport test2: vc-7_1-stlport test4: vc-7_1-stlport test5: vc-7_1-stlport vc-7_1-stlport |parameter| duplicates: borland-5_6_4 borland-5_8_2 maybe: vc-6_5 vc-6_5-stlport vc-7_0 preprocessor: borland-5_6_4 borland-5_8_2 sun-5.8 vc-6_5 vc-6_5-stlport python-parameter-test: vc-6_5 vc-6_5-stlport vc-7_0 sfinae: borland-5_8_2 vc-6_5-stlport singular: borland-5_6_4 borland-5_8_2 unnamed_fail: vc-6_5 vc-6_5-stlport vc-7_0 |program_options| cmdline_test_dll: cw-9.4 options_description_test_dll: cw-9.4 parsers_test_dll: cw-9.4 positional_options_test_dll: cw-9.4 unicode_test_dll: borland-5_8_2 cw-9.4 variable_map_test_dll: borland-5_8_2 cw-9.4 winmain_dll: cw-9.4 |python| args: sun-5.8 data_members: sun-5.8 defaults: sun-5.8 exec: cw-9.4 darwin-4.0.1 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp numpy: gcc-3.3.6 gcc-3.4.4 sun-5.8 pickle3: sun-5.8 polymorphism2_auto_ptr: sun-5.8 select_from_python_test: darwin-4.0.1 slice: gcc-3.3.6 gcc-3.4.4 sun-5.8 string_literal: sun-5.8 wrapper_held_type: sun-5.8 |random| random_test: intel-linux-9.0 |rational| rational_test: borland-5_6_4 vc-6_5 vc-6_5-stlport vc-7_0 |regex| regex_regress_threaded: gcc-4_0_3_tru64 |serialization| test_class_info_load_text_warchive: vc-6_5 test_demo: msvc-8.0 test_non_default_ctor2_text_archive: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_non_default_ctor2_text_archive_dll: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_non_default_ctor2_text_warchive: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_non_default_ctor2_text_warchive_dll: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_reset_object_address: vc-7_0 test_reset_object_address_dll: vc-7_0 test_simple_class_binary_archive_dll: vc-6_5 test_simple_class_text_archive_dll: vc-6_5 test_simple_class_text_warchive_dll: vc-6_5 test_simple_class_xml_archive_dll: vc-6_5 test_simple_class_xml_warchive_dll: vc-6_5 test_tracking_binary_archive: msvc-8.0 test_variant_xml_archive: borland-5_8_2 test_variant_xml_archive_dll: borland-5_8_2 test_variant_xml_warchive: borland-5_8_2 test_variant_xml_warchive_dll: borland-5_8_2 |signals| dead_slot_test: gcc-3.3.6 gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp qcc-3.3.5_gpp trackable_test: gcc-3.3.6 gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp qcc-3.3.5_gpp |spirit| mix_and_match_trees: sun-5.8 |test| parameterized_test_test: vc-6_5 vc-6_5-stlport |tr1| run_random: sun-5.8 std_run_complex_overloads: msvc-8.0 sun-5.8 std_run_random: sun-5.8 std_test_bind: sun-5.8 std_test_complex: sun-5.8 std_test_function: sun-5.8 std_test_hash: sun-5.8 std_test_mem_fn: sun-5.8 std_test_random: sun-5.8 std_test_reference_wrapper: sun-5.8 std_test_reference_wrapper_tricky: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux_x86_64 intel-linux-9.0 mingw-3_4_2 msvc-7.1 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp vc-7_1-stlport std_test_result_of: sun-5.8 std_test_shared_ptr: sun-5.8 std_test_tuple: sun-5.8 std_test_tuple_tricky: sun-5.8 std_test_type_traits: sun-5.8 test_boost: vc-7_1-stlport test_hash: vc-7_1-stlport test_random: sun-5.8 vc-7_1-stlport test_reference_wrapper_tricky: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux_x86_64 intel-linux-9.0 mingw-3_4_2 msvc-7.1 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp test_regex: vc-7_1-stlport test_type_traits: sun-5.8 |typeof| function_binding_native: vc-6_5 vc-6_5-stlport vc-7_0 nested_typedef_emulation: cw-9.4 odr_no_uns: vc-6_5 vc-6_5-stlport vc-7_0 template_tpl_emulation: sun-5.8 |utility| operators_test: gcc-3.4.5_linux_x86_64 |wave| test_re2c_lexer: msvc-8.0 test_slex_lexer: msvc-8.0 testwave_dll: msvc-8.0

1 0

Re: [boost] Exception Visitor
by Ames Andreas 12 Aug '06

12 Aug '06

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Alexander Nasonov > Sent: Friday, July 28, 2006 12:54 PM > Subject: Re: [boost] Exception Visitor > > Please, NO! > It's my experience that one catch(...) in a program may be a > source of many annoying glitches that users report > periodically but developers don't understand what's going on. > Removing this often helps. Users start reporting crashes. > Most difficult at this stage is to find a user who is able to > run Dr. Watson, check 'Create Crash Dump File' and send a > dump to developers :) > > Also worth noting that SEH is not standard C/C++. FWIW, I'd like to strongly second that. When catching SEH exceptions (like catch(...) does), predictable behaviour is only possible if you compile for 'asynchronous exception handling', which according to the docs increases the generated code size (I don't know about the runtime performance cost). If you compile for 'synchronous exception handling' (the more usual thing, I believe), you should either be prepared to live with bad cleanup of the stack or you install a global SEH-exception handler in each thread you start, which does nothing but rethrow and therefore crash the app. IMHO, that's nothing a library should impose on its apps. Anyway, I fail to see what's the benefit of catching segfaults _as the default behaviour_ (that's not to say there aren't applications that need to do). FWIW again, I won't use a solution which includes catch(...) anytime soon (and esp. not if it's done in a pervasive manner). cheers, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | ames AT avaya DOT com

5 6

Re: [boost] Proposed library Boost Exception updated
by Emil Dotchevski 12 Aug '06

12 Aug '06

Pavel, > "Emil Dotchevski" wrote: > > > http://www.revergestudios.com/boost-exception/boost-exception.html > > > > It is also possible to extend the interface to support enumeration of > > the > > exception info stored in boost::exception objects, but my personal > > preference is to first collect more feedback from people using the > > library, > > because I'm not sure if this enumeration is needed in practice. Brad > > King > > illustrated this idea in his earlier post: > > > > http://article.gmane.org/gmane.comp.lib.boost.devel/146322 > > > > I believe this functionality should be present > and will be used extensively at the top level > of an application. Could you provide an example of using this functionality at the top level of an application? > There should be also ability to support > visitation of exception objects. > Imagine situation: > > try { > .... > } catch (boost::exception& e) { > e << ....; > > // now some exceptions could be handled > // and some need to be passed up > ???? > > > The ??? could be typeswitch or it could > be a visitor object passed into the exception. > The visitor would be able to throw original > or new exception or handle the situation. > The visitor could be separated, reused > and is more dynamic than a typeswitch. I am not sure I understand what you mean by typeswitch. Can you illustrate your point with more code? --Emil

3 10

[random][lognormal_distribution] compilation error
by Roman Yakovenko 11 Aug '06

11 Aug '06

boost(a)lists.boost.org Hi. Instantiation of class lognormal_distribution<double> could not be compiled. Error message: D:\boost_cvs\boost\random\lognormal_distribution.hpp(63) : error C2440: 'return' : cannot convert from 'const double' to 'double &' Conversion loses qualifiers D:\boost_cvs\boost\random\lognormal_distribution.hpp(63) : while compiling class-template member function 'double &boost::lognormal_distribution<>::mean(void) const' dev\boost_random\random_export.hpp(323) : see reference to class template instantiation 'boost::lognormal_distribution<>' being compiled I think that "mean" and "sigma" functions should have return type RealType instead of RealType&. RealType& mean() const { return _mean; } ==> RealType mean() const { return _mean; } RealType& sigma() const { return _sigma; } ==> RealType sigma() const { return _sigma; } Thanks -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/

2 1

Re: [boost] Boost inspection notification (2006-08-09/RC_1_34_0) *X*
by Alexander 11 Aug '06

11 Aug '06

It's uneasy to find new Boost inspection notification at my client. I spend near 5 minutes just to find this notification. May be making special brunch for notifications not such a good idea? Regards, Alexander

2 3

[test] Buglet in floating point comparison code.
by John Maddock 11 Aug '06

11 Aug '06

I'm using Boost.Test, specifically BOOST_CHECK_CLOSE with non-built-in floating point types. In particular I have a type "real_concept" that models the concepts I want an arbitrary real number type to adhere to. This type does *not* specialise std::numeric_limits: deliberately so because I want to support types with whose precision varies at runtime. This causes a problem inside safe_fpt_division which uses std::numeric_limits without the check to see if it's specialised or not. In turn this causes almost all comparisons using real_concept to succeed because safe_fpt_division will almost always return 0 for real_concept. The obvious fix is simply to place the numeric_limits checks inside an if(std::numeric_limits<FPT>::is_specialized) block, and to perform no safety checks in this case and just go ahead and perform the division regardless (there are no checks that can be performed in this case anyway). Thanks, John.

3 12

[utility] nonconstructible
by Chris Weed 11 Aug '06

11 Aug '06

Hi, I think it would be nice to have a "nonconstructible" class to derive from similar to noncopyable. Recently I was burned by a traits class that was getting constructed. I think this should also be used for template metafunctions. I envision something like the following: struct nonconstructible { private: nonconstructible() {} } template<typename T> struct my_traits : nonconstructible { typedef int my_type; }; Chris

3 4