- Boost-users - lists.boost.org

Re: [Boost-users] Thread cancellation
by Sliwa, Przemyslaw (London) 30 Aug '05

30 Aug '05

Zthread looks promising but there is no documentation at all. In addition there is no mailing list. Pshemek -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Charles BROSSOLLET Sent: 30 August 2005 12:52 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Thread cancellation The ZThreads library supports thread cancellation, but I haven't tried it. Does anyone who have an experience with both libraries could share what he thinks of each one? Regards -- Charles ----- Original Message ----- From: Janusz Piwowarski To: boost-users(a)lists.boost.org Sent: Tuesday, August 30, 2005 11:52 AM Subject: Re: [Boost-users] Thread cancellation Sliwa, Przemyslaw (London) wrote: > Can anyone tell me if it is possible to cancel a thread using > boost.thread library? Form Boost.Thread FAQ: Q: Why isn't thread cancellation or termination provided? A: There's a valid need for thread termination, so at some point Boost.Threads probably will include it, but only after we can find a truly safe (and portable) mechanism for this concept. Regards, -- Janusz _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

1 0

Boost.Signals: Suspicious workaround tests
by Daniel Krügler 30 Aug '05

30 Aug '05

Yesterday I stumbled about the following tests in boost 1.33: In signals/detail/named_slot_map.hpp: class named_slot_map_iterator { .. #if BOOST_WORKAROUND(_MSC_VER, <= 0x1701) ... }; In signals/signal_template.hpp class BOOST_SIGNALS_SIGNAL { ... #if BOOST_WORKAROUND(BOOST_MSVC, <= 0x1700) ... }; Are these tests really correct?? I am wondering because _MSC_VER has the following values (decimal!!) VC6: 1200 VC7: 1300 VC7.1: 1310 which does not fit to those hexadecimal values, which would correspond to version number 5888 and 5889 (!). I know that boost coworkers often have good contacts to compiler providers, but that good ... ;-)) Greetings from Bremen, Daniel Krügler

2 1

[assign] Some basic questions (lengthy code example)
by Ames Andreas 30 Aug '05

30 Aug '05

Hi all, I could use some advice regarding this lengthy code example: ---------- <code> ------------ #include <vector> #include <map> #include <boost/function.hpp> #include <boost/assign.hpp> struct E1 {}; struct E2 {}; enum State { eS1 = 1, eS2 }; typedef boost::function< bool (const E1 &, int) > function0_t; typedef boost::function< bool (const E2 &, int) > function1_t; struct Functions { // Functions(std::vector< function0_t > af0 , std::vector< function1_t > af1) // : f0(af0) , f1(af1) // { // } std::vector< function0_t > f0; std::vector< function1_t > f1; }; struct Handler1 { bool operator()(const E1&, int) {return true;} }; struct Handler1a { bool operator()(const E1&, int) {return true;} }; struct Handler2 { bool operator()(const E2&, int) {return true;} }; typedef std::map< State, Functions > InitDesc; using namespace boost::assign; int main() { // [1] this works just fine Functions f1 = { list_of(Handler1()), list_of(Handler2())}; // [2] this doesn't work cause Handler1 and Handler1a have different types Functions f2 = { list_of(Handler1())(Handler1a()), list_of(Handler2())}; // [3] don't know how to do this InitDesc desc = map_list_of(eS1, {list_of(Handler1()), list_of(Handler2())}) (eS2, {list_of(Handler1a()), list_of(Handler2())}); } ---------- </code> ------------ The places marked with [1], [2] and [3] are of special interest for me. I like [1] very much thanks to what bost::assign offers me. Unfortunately I can get [2] only to work, if I explicitly create instances of function0_t from Handler1 and Handler1a. Are there more elegant ways to make this work? [3] is obviously broken, but I don't know how to come up with a similarly compact way to initialise an InitDesc instance. I can uncomment Funtions' constructor above and call it explicitely with what I've written into curly braces but that unfortunately breaks [1] (because Functions is no longer aggregate then). Is there a better way to do it prefarably without breaking [1]? TIA, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

1 0

Re: [Boost-users] Regex boost 1.33 - (mingw/w32) linking
by Arno Mauhourat 30 Aug '05

30 Aug '05

2 1

Compilation with comeau
by pisalmon＠numericable.fr 30 Aug '05

30 Aug '05

Hi I have some problem to compile boost 1.32 with comeau. I use como 4.33 + gcc 3.3.5 on Linux Ubuntu. During the comilation I have some error : ...found 4271 targets... ...updating 489 targets... como-C++-action bin/boost/libs/test/build/libboost_prg_exec_monitor.so/como/debug/execution_monitor.o Comeau C/C++ 4.3.3 (Oct 24 2003 16:00:23) for RedHat_LINUX_INTEL_ELF Copyright 1988-2003 Comeau Computing. All rights reserved. MODE:non-strict warnings C++ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/bcs_char_traits.hpp", line 64: error: namespace "std" has no member "size_t" static int compare( const_char* cstr1, const_char* cstr2, std::size_t n ) ^ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/bcs_char_traits.hpp", line 77: error: namespace "std" has no member "size_t" static std::size_t length( const_char* cstr ) ^ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/bcs_char_traits.hpp", line 88: error: namespace "std" has no member "size_t" static const_char* find( const_char* s, std::size_t n, CharT c ) ^ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/basic_cstring.hpp", line 47: error: namespace "std" has no member "size_t" typedef std::size_t size_type; ^ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/basic_cstring.hpp", line 48: error: namespace "std" has no member "ptrdiff_t" typedef std::ptrdiff_t difference_type; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 92: error: namespace "std" has no member "size_t" const std::size_t REPORT_ERROR_BUFFER_SIZE = 512; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 301: error: identifier "sigjmp_buf" is undefined static sigjmp_buf& jump_buffer() ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 310: error: incomplete type is not allowed struct sigaction m_same_action_for_all_signals; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 311: error: incomplete type is not allowed struct sigaction m_old_SIGFPE_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 312: error: incomplete type is not allowed struct sigaction m_old_SIGTRAP_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 313: error: incomplete type is not allowed struct sigaction m_old_SIGSEGV_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 314: error: incomplete type is not allowed struct sigaction m_old_SIGBUS_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 315: error: incomplete type is not allowed struct sigaction m_old_SIGABRT_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 316: error: incomplete type is not allowed struct sigaction m_old_SIGALRM_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 318: error: identifier "sigjmp_buf" is undefined sigjmp_buf m_sigjmp_buf; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 335: error: identifier "siglongjmp" is undefined siglongjmp( signal_handler::jump_buffer(), sig ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 352: error: identifier "sigemptyset" is undefined sigemptyset( &m_same_action_for_all_signals.sa_mask ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 356: error: incomplete type is not allowed sigaction( SIGFPE , &m_same_action_for_all_signals, &m_old_SIGFPE_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 356: error: expected a ")" sigaction( SIGFPE , &m_same_action_for_all_signals, &m_old_SIGFPE_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 357: error: incomplete type is not allowed sigaction( SIGTRAP, &m_same_action_for_all_signals, &m_old_SIGTRAP_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 357: error: expected a ")" sigaction( SIGTRAP, &m_same_action_for_all_signals, &m_old_SIGTRAP_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 358: error: incomplete type is not allowed sigaction( SIGSEGV, &m_same_action_for_all_signals, &m_old_SIGSEGV_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 358: error: expected a ")" sigaction( SIGSEGV, &m_same_action_for_all_signals, &m_old_SIGSEGV_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 359: error: incomplete type is not allowed sigaction( SIGBUS , &m_same_action_for_all_signals, &m_old_SIGBUS_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 359: error: expected a ")" sigaction( SIGBUS , &m_same_action_for_all_signals, &m_old_SIGBUS_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 360: error: incomplete type is not allowed sigaction( SIGABRT, &m_same_action_for_all_signals, &m_old_SIGABRT_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 360: error: expected a ")" sigaction( SIGABRT, &m_same_action_for_all_signals, &m_old_SIGABRT_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 364: error: incomplete type is not allowed sigaction( SIGALRM , &m_same_action_for_all_signals, &m_old_SIGALRM_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 364: error: expected a ")" sigaction( SIGALRM , &m_same_action_for_all_signals, &m_old_SIGALRM_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 379: error: incomplete type is not allowed sigaction( SIGALRM, &m_old_SIGALRM_action, sigaction_ptr() ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 379: error: expected a ")" sigaction( SIGALRM, &m_old_SIGALRM_action, sigaction_ptr() ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 383: error: incomplete type is not allowed sigaction( SIGFPE , &m_old_SIGFPE_action , sigaction_ptr() ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 383: error: expected a ")" sigaction( SIGFPE , &m_old_SIGFPE_action , sigaction_ptr() ); apparently, como don't find some type in std but i use libcomo and is correctly installed. If you have some idea Best regards

1 0

Boost.Random: Missing definitions of to static constants
by Daniel Krügler 30 Aug '05

30 Aug '05

The class template xor_combine<> from xor_combine.hpp declares 3 static constant members has_fixed_range (bool), shift1 (int), and shift2 (int), but **defines** only has_fixed_range. I propose, that proper definitions for shift1 and shift2 should be provided in the already existing BOOST_NO_INCLASS_MEMBER_INITIALIZATION block, too. Greetings from Bremen, Daniel Krügler

1 0

incorrect random library equality implementation?
by Steven Solie 30 Aug '05

30 Aug '05

The Boost 1.33.0 random library equality operators seem to be implemented incorrectly. For example, in file random/lagged_fibonacci.hpp starting at line 390 we have the following: friend bool operator==(const lagged_fibonacci_01& x, const lagged_fibonacci_01& y) { return x.i == y.i && std::equal(x.x, x.x+long_lag, y.x); } The std::equal() call is comparing an array of doubles using operator == which I thought was impossible for floating point types due to their inexact nature et al. This is causing all the test cases using floating point types to fail on AmigaOS with GCC 3.4.4. Is this an implementation error or am I missing something? --Steven

2 1

boost::thread waiting problem
by Ovanes Markarian 30 Aug '05

30 Aug '05

Hello, I have the following scenario: Evaluate String Stream until a certain string is found or a time has occured. The string evaluation is made not in a single function, but using a stream iterator and later an evaluator of the retrieved data. I have an iterator class as function object where a boost::shared_ptr<boost::timed_mutex> mutex; member is defined. It has 2 functions: operator()() which is a worker function of the time_out thread and an iteratorion function. Now I start when entered for the first time the iteration function the time_out thread. The time_out thread should block until the time_out elapses or the another function has found the desired string from the stream. my code looks like: operator()() { boost::timed_mutex::scoped_timed_lock lock(*mutex, true); boost::condition c; boost::xtime xt; boost::xtime_get(&xt, boost::TIME_UTC); xt.sec +=20; c.timed_wait(lock, xt); } My approach was to use the mutex object for syncronization. I assumed that it is locked as long as c.timed_wait(...) is waiting. So I try to lock this object in the other thread. If the mutex object can not be locked the worker thread is still waiting, otherwise time_out elapsed. >From the Rationale section of the thread docs I heavily understand which locking strategy is used for timed_mutex. Can someone point me to a the correct place with documentation and say if this approach will work or I should consider a redesign? With Kind Regards, Ovanes Markarian

1 0

Re: [Boost-users] [boost::bind] How use with fn objects?
by BRIDGES Dick 30 Aug '05

30 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Rene Rivera > Sent: Monday, August 29, 2005 12:30 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [boost::bind] How use with fn objects? > > BRIDGES Dick wrote: [snip] > > I'm trying to pass a function object that takes no > > parameters to a boost::thread constructor and cannot > > get it right. [snip] > Either: > > int > main( int argc, char **argv ) { > Foo f; > boost::thread doit( boost:bind(Foo::operator(),&f)() ); > doit.join(); > return 0; > } > > Or: > > int > main( int argc, char **argv ) { > Foo f; > boost::thread doit( f ); > doit.join(); > return 0; > } > > Should work. > > > -- > -- 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 After I figured out I had to use boost::ref(f) with my real class, the second form worked fine. I had a problem with the first form though. <code> boost::thread doit( boost::bind(Foo::operator(),&f)() ); </code> Yielded the following [edited to fit] result: <result> g++ -D_REENTRANT -I/usr/local -I/usr/local/boost_1_33_0 -I/usr/local/include -O0 -g3 -Wall -c -fmessage-length=0 -Wno-non-virtual-dtor -omain.o ../main.cpp ../main.cpp: In function `int main(int, char**)': ../main.cpp:22: error: invalid use of non-static member function `void my_namespace::Foo::operator()()' /usr/local/boost_1_33_0/boost/bind.hpp: At global scope: /usr/local/boost_1_33_0/boost/bind.hpp: In instantiation of `boost::_bi::result_traits<boost::_bi::unspecified, void (my_namespace::Foo::)()>': /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:15: instantiated from `boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >' ../main.cpp:22: instantiated from here /usr/local/boost_1_33_0/boost/bind.hpp:63: error: `void (my_namespace::Foo::)()' is not a class, struct, or union type /usr/local/boost_1_33_0/boost/bind/bind_template.hpp: In instantiation of `boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >': ../main.cpp:22: instantiated from here /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:15: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (my_namespace::Foo::)()>' /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:18: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (my_namespace::Foo::)()>' [snip bind_template.hpp:24 thru bind_template.hpp:138] /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:143: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (my_namespace::Foo::)()>' /usr/local/boost_1_33_0/boost/bind.hpp: In instantiation of `boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >': ../main.cpp:22: instantiated from here /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:160: error: field `boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >::f_' invalidly declared method type ../main.cpp: In function `int main(int, char**)': ../main.cpp:22: error: no match for call to `(boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >) ()' /usr/local/boost_1_33_0/boost/bind.hpp: In constructor `boost::_bi::bind_t<R, F, L>::bind_t(F, const L&) [with R = boost::_bi::unspecified, F = void (my_namespace::Foo::)(), L = boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> >]': /usr/local/boost_1_33_0/boost/bind.hpp:1403: instantiated from `boost::_bi::bind_t<boost::_bi::unspecified, F, typename boost::_bi::list_av_1<A1>::type> boost::bind(F, A1) [with F = void (my_namespace::Foo::)(), A1 = my_namespace::Foo*]' ../main.cpp:22: instantiated from here /usr/local/boost_1_33_0/boost/bind.hpp:861: error: invalid use of non-static member function make: *** [main.o] Error 1 make: Target `all' not remade because of errors. </result> Thank you (and Peter Dimov) for your assistance. BTW I'm still unclear on *why* (f) works. It doesn't look like any pointer to member function I've read about. Isn't f.operator() treated like any other member function? Can someone suggest something to read that might help me understand? Thanks again for your help. Regards, Dick Bridges

2 1

[Threads] Doc build error?
by Bruno Martínez 30 Aug '05

30 Aug '05

The documentation of boost.threads seems to be built wrong. In several places sentences don't make sense, and words are missing. Some examples are: " Introduction ??? allows C++ programs to execute as multiple, asynchronous, independent threads-of-execution. " " It is possible to write thread-safe implementations of these by using thread specific storage (see boost::thread_specific_ptr), and several C++ compiler vendors do just that. The technique is well-know and is explained in ???. " What's wrong? Bruno

1 0