- Boost - lists.preview.boost.org

[date time] std::out_of_range thrown on date 2012-5-29
by Matthijs Möhlmann 09 Aug '13

09 Aug '13

Hello all, Following piece of program gives a std::out_of_range exception: #include <boost/date_time/posix_time/posix_time.hpp> int main(int argc, char **argv) { boost::posix_time::ptime datetime; datetime = boost::posix_time::time_from_string("2012-5-29"); return 0; } Compiled with the following line: g++ -o main -lboost_date_time -g -std=c++11 main.cpp Output: matthijs@hammer % ./main terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at zsh: abort ./main Platform: x86_64 Boost version: 1.54 Compiler version: gcc 4.8 Where can I officially report bugs? Regards, Matthijs Möhlmann

3 3

[move] forward with lvalue ref template param
by Andrew Ho 08 Aug '13

08 Aug '13

Hi during my implementation of unique_ptr I noticed that boost::forward doesn't play nicely with lvalue ref types. int a; int &b = a; int &c = std::forward<int&>(b); // compiles fine int &d = boost::forward<int&>(b); // compiler error I did a little playing around with the declarations of forward and I managed to get this to work: // if T is not a lvalue ref and movable template <class T> inline typename ::boost::move_detail::enable_if_c < enable_move_utility_emulation<T>::value && ::boost::move_detail::is_rv<T>::value && !::boost::move_detail::is_lvalue_reference<T>::value, const T &>::type forward(typename ::boost::move_detail::identity<T>::type &x) BOOST_NOEXCEPT { return const_cast<T&>(x); } // if T is not a lvalue ref and not movable template <class T> inline typename ::boost::move_detail::enable_if_c < enable_move_utility_emulation<T>::value && !::boost::move_detail::is_rv<T>::value && !::boost::move_detail::is_lvalue_reference<T>::value, const T &>::type forward(const typename ::boost::move_detail::identity<T>::type &x) BOOST_NOEXCEPT { return x; } // if T is a lvalue ref template <class T> inline typename ::boost::move_detail::enable_if_c < ::boost::move_detail::is_lvalue_reference<T>::value , T>::type forward(T x) BOOST_NOEXCEPT { return x; } Basically, this forces all calls to forward<A&> to simply return the lvalue ref (const-ness is maintained, I think), otherwise it does whatever boost::forward did before. As far as I can tell, this doesn't break boost::forward, and it enables it to properly handle taking lvalue refs. Am I right in my assumptions? Are there any cases where this would fail to produce standard-compliant/desired results?

1 0

[git] eol issues and fetchRecurseSubmodules = on-demand
by Ahmed Charles 08 Aug '13

08 Aug '13

Two things: 1. tools\build\v2\engine\build.bat has LF instead of CRLF for line endings, which causes bootstrap.bat (which has the right endings) to not work properly. It seems like the top level .gitattributes doesn't apply to submodules. 2. After cloning and fetching modular boost each day for a while, I finally figured that waiting an hour or so to sync could probably be improved. So I read the docs and tested adding fetchRecurseSubmodules = on-demand for each submodule in .gitsubmodules and it seems to work much faster with the same result. (It would result in differences once the submodules can change without the super-project changing, but currently, I don't think that is the case.) Perhaps it's with considering?

2 5

[boost/spirit] numeric policy
by Brian Schrom 07 Aug '13

07 Aug '13

I've had the case where I needed to retain formatting information for a number (general, fixed, scientific) and was nicely accomplished by extending the policy, but needed to have a begin_parse() and end_parse() for the policy to be complete. It seems that it makes some sense or is this accomplished another way? Maybe something to consider for policies in general? Index: qi/numeric/real_policies.hpp =================================================================== --- qi/numeric/real_policies.hpp (revision 85166) +++ qi/numeric/real_policies.hpp (working copy) @@ -28,6 +28,18 @@ static bool const allow_trailing_dot = true; static bool const expect_dot = false; + template <typename Attribute> + static void + begin_parse(Attribute& attr_) + { + } + + template <typename Attribute> + static void + end_parse(Attribute& attr_,bool /* result */) + { + } + template <typename Iterator> static bool parse_sign(Iterator& /*first*/, Iterator const& /*last*/) Index: qi/numeric/detail/real_impl.hpp =================================================================== --- qi/numeric/detail/real_impl.hpp (revision 85166) +++ qi/numeric/detail/real_impl.hpp (working copy) @@ -133,6 +133,7 @@ parse(Iterator& first, Iterator const& last, Attribute& attr, RealPolicies const& p) { + p.begin_parse(attr); if (first == last) return false; Iterator save = first; @@ -257,6 +258,7 @@ // If we got a negative sign, negate the number traits::assign_to(traits::negate(neg, n), attr); + p.end_parse(attr, true); // maybe this should return a bool and be the return value? // Success!!! return true; }

4 7

[intrusive] Compilation problem with gcc 4.7
by Hartmut Kaiser 07 Aug '13

07 Aug '13

In code which compiled just fine I'm now seeing: In file included from /opt/boost/trunk-debug/boost/intrusive/slist_hook.hpp:24:0, from /opt/boost/trunk-debug/boost/intrusive/slist.hpp:21, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/lcos/local/mu tex.hpp:23, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/runtime/compo nents/server/wrapper_heap.hpp:20, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/runtime/compo nents/server/managed_component_base.hpp:13, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/lcos/base_lco .hpp:12, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/lcos/base_lco _with_value.hpp:11, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/performance_c ounters/counters.hpp:12, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/runtime/compo nents/server/runtime_support.hpp:32, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/runtime.hpp:1 2, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/src/hpx_main.cpp: 7: /opt/boost/trunk-debug/boost/intrusive/detail/generic_hook.hpp: At global scope: /opt/boost/trunk-debug/boost/intrusive/detail/generic_hook.hpp:134:55: error: declaration of typedef struct boost::intrusive::hooktags<typename GetNodeAlgorithms::type::node_traits, Tag, LinkMode, BaseHookType> boost::intrusive::generic_hook<GetNodeAlgorithms, Tag, LinkMode, BaseHookType>::hooktags [-fpermissive] /opt/boost/trunk-debug/boost/intrusive/detail/generic_hook.hpp:84:8: error: changes meaning of hooktags from struct boost::intrusive::hooktags<typename GetNodeAlgorithms::type::node_traits, Tag, LinkMode, BaseHookType> [-fpermissive] Ion, could you fix this, please? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu

2 2

MinGW test failures
by Andrey Semashev 07 Aug '13

07 Aug '13

Hi, I can see that almost all MinGW tests (jc-bell.com runner) for trunk are failing, at least for Boost.Log [1] and Boost.Atomic [2]. However, test logs don't show any errors, only compiler warnings. Does anyone know what is the problem? Also, this is not the first time when I see no errors in logs while the test is marked as failed. This is really unhelpful. Are some logs being lost by the test running suite? [1] http://www.boost.org/development/tests/trunk/developer/log.html [2] http://www.boost.org/development/tests/trunk/developer/atomic.html

2 1

[predef] Boost detail/endian.hpp
by Rene Rivera 07 Aug '13

07 Aug '13

FYI.. I just tested, locally, and checked in the replacement for the "boost/detail/endian.hpp". This file is now non-BSL license free. If this is a header you rely on I would appreciate it if you could do your own testing to make sure it lives up to the previous header's functionality. Thanks, Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

2 1

Re: [boost] Removing old config macro and increasing compiler requirements.
by Brian Wood 07 Aug '13

07 Aug '13

Dave Abrahams wrote: >>on Tue Aug 06 2013, Brian Wood <woodbrian77-AT-gmail.com> wrote: >> >> I was going to ask for an update on these things, but this >> will do. I think it's just morass without an e. It sounds like >> it's time to reboot. I haven't followed this real closely, but >> know a lot of effort has gone into trying to preserve >> information in the conversion. That may be too much to ask. > > Boy, you really haven't been paying attention: that part is done. > Throwing out all that work at this point because you get the sense "it's > time to reboot" would be... well, pick your adjective. Too many are > flying through my brain right now to choose. I thought the use of the word morass was honest and putting it mildly. I'm not saying to abandon the goal. I recommend a modular approach, but it seems the years are passing without much happening. -- Brian Wood Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

1 0

Re: [boost] Removing old config macro and increasing compiler requirements.
by Brian Wood 07 Aug '13

07 Aug '13

Dave Abrahams wrote: > That's how Boost works. One of the ideas of the Git separation (and > hopefully eventual Ryppl) transition is to give maintainers more of a > sense of control over these things. I'm sure the commitment to quality > is there, but I think there's probably a lot of resignation over the > seemingly-intractable morasse. I was going to ask for an update on these things, but this will do. I think it's just morass without an e. It sounds like it's time to reboot. I haven't followed this real closely, but know a lot of effort has gone into trying to preserve information in the conversion. That may be too much to ask. -- Brian Wood Ebenezer Enterprises - So far G-d has helped us. http://webEbenezer.net

3 2

[mpl] at<> example bug?
by Mostafa 06 Aug '13

06 Aug '13

Looks like the example found here: http://www.boost.org/doc/libs/1_54_0/libs/mpl/doc/refmanual/at.html is buggy: BOOST_MPL_ASSERT_RELATION( (at< range, int_<0> >::value), ==, 10 ); It should be: BOOST_MPL_ASSERT_RELATION( (at< range, int_<0> >::type::value), ==, 10 ); Mostafa

3 3

How do folks test serialization code?
by John Maddock 06 Aug '13

06 Aug '13

Title almost says it all, how do you verify that your classes serialization code is truly platform independent, and doesn't accidently break later? I have some trivial tests that round trip to a stringstream using boost::archive::text_i/oarchive, but of course that only verifies that platform-specific serialization works. So what do folks do - generate text archives on different platforms, deserialize and compare? How does Boost.Serialization itself verify this? Cheers, John.

6 17

[git] Deleted file in detail module
by Daniel James 05 Aug '13

05 Aug '13

Hi, I just look in the detail module, and it contains this file: boost/functional/detail/container_fwd.hpp This file was deleted from trunk in r80288 and from release in r81356. https://svn.boost.org/trac/boost/changeset/80288 https://svn.boost.org/trac/boost/changeset/81356 Would it be possible to reflect that? Btw. I would have put it in functional, but that isn't a big deal. thanks, Daniel

2 1

[move] Documentation example typo.
by Jurko Gospodnetić 04 Aug '13

04 Aug '13

Hi. Just reporting a slight typo in boost::move library documentation's file_descriptor class example code for closing the OS file descriptor. It says: > if(!os_descr_) operating_system_close_file(os_descr_); in its destructor & assignment operator when it should in fact say: > if(os_descr_) operating_system_close_file(os_descr_); [notice the removed ! operator] Hope this helps. Best regards, Jurko Gospodnetić

2 1

[asio] condition_variable for coroutine-powered ASIO
by TONGARI J 04 Aug '13

04 Aug '13

Hi, Since Boost 1.54, ASIO introduced yield_context, which is very helpful to alleviate the pain of writing async ops. Unlike multi-threading, with cooperative multi-tasking, generally we don't have to worry about synchronization, but we still need some sort of mechanism to sync the coroutines in cases like producer-consumer for waiting the data... While I haven't seen any sync tool for asio/coroutine, having a condition_variable or such may be very useful, what do you think? Attached is the poor-man's implementation...

2 1

[timer] May I apply trivial fix?
by Antony Polukhin 03 Aug '13

03 Aug '13

Hi, As far as I know Beman is almost always busy, so may I apply trivial fix described in this ticket https://svn.boost.org/trac/boost/ticket/8956 ? This fix is essential for running regression tests with Intel compiler. -- Best regards, Antony Polukhin

5 6

[utility] [swap] How about Boost.Move?
by Antony Polukhin 03 Aug '13

03 Aug '13

Hi, Sources of Boost.Variant have a swap implementation that takes advantage of move emulation. That code can be useful for Boost.Swap. The idea is not to use std::swap in case of ADL failure, but use a swap implementation that is aware of move emulation: namespace boost_swap_impl { namespace swap_move_emulated { template <typename T> inline void swap(T& lhs, T& rhs) { T tmp( boost::move(lhs) ); lhs = boost::move(rhs); rhs = boost::move(tmp); } } template<class T> void swap_impl(T& left, T& right) { //using namespace std;//use std::swap if argument dependent lookup fails using namespace boost_swap_impl::swap_move_emulated; swap(left,right); } // ... With that code types that use move emulation can be swapped faster and even move only types can be swapped. So, what do the community think about such optimization? -- Best regards, Antony Polukhin

5 8

boost::lockfree::spsc_queue and destructors
by Taylor Holliday 03 Aug '13

03 Aug '13

Hey Boost, I was passing some shared_ptrs between threads using a boost::lockfree::spsc_queue and it would seem that the shared_ptr destructor isn't called upon popping from the queue. So spsc_queue differs from a typical queue in that regard. Why is that? thanks! - Taylor

2 1

[git-help] New libraries?
by Rene Rivera 03 Aug '13

03 Aug '13

Today I checked in the new Predef library and I'm wondering, not just for it but in general, if this interim period of svn to git transition what happens to new libraries? Will they automatically show up in the git repos? What are the procedures if the new library is already, originally in git and modularized? Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

3 5

Reboot of the boost server machine
by DongInn Kim 02 Aug '13

02 Aug '13

Dear All, For the system maintenance, we need to reboot the following server machines today. I am sorry for such a short notice. - milliways - eddie - wowbagger (Boost websites and mailing lists) - deep-thought (NFS server) Date: Aug 2, 2013 Time: 4:00pm-4:30pm (E.T.) - 1:00pm-1:30pm Pacific US time - 2:00pm-2:30pm Mountain US time - 3:00pm-3:30pm Central US time - 4:00pm-4:30pm Eastern US time - 8:00pm-8:30pm GMT The following services would not be available during the system maintenance. - Web services (e.g., www.boost.org) - Subversion (e.g., svn.boost.org) - mailing lists (e.g., boost(a)lists.boost.org, …) - Login to the NFS $HOME mounted system - Mail archives - Send mail - NFS Please let me know if you have any issues or questions about this sudden reboot. Regards, -- - DongInn

1 0

Suppressing boost.thread and boost.system symbols in shared library
by Philip Bennefall 02 Aug '13

02 Aug '13

Hi all, I am building a shared library for Linux, for which I would like to export as few symbols as possible (ideally only the functions that my library users actually need to call). When building my project, I have the following options: -fvisibility=hidden -fvisibility-inlines-hidden I then mark all the functions that I am exporting as having default visibility. I link to static versions of boost.thread and boost.system. When I then say: nm -DC libtest.so I get a large number of symbols such as: 0002abe0 V typeinfo name for boost::exception_detail::clone_impl<boost::exceptio n_detail::bad_exception_> 0002ace0 V typeinfo name for boost::exception_detail::bad_exception_ 00029920 V typeinfo name for boost::exception_detail::error_info_injector<boost: :lock_error> 00029b00 V typeinfo name for boost::exception_detail::error_info_injector<boost: :condition_error> 00029860 V typeinfo name for boost::exception_detail::error_info_injector<boost: :thread_resource_error> 0002970f V typeinfo name for boost::thread_exception 00029a7b V typeinfo name for boost::thread_interrupted 00029740 V typeinfo name for boost::thread_resource_error 0002ac40 V typeinfo name for boost::enable_shared_from_this<boost::detail::threa d_data_base> 0002a720 V typeinfo name for boost::detail::thread_data_base 0002ad20 V typeinfo name for boost::detail::sp_counted_impl_p<boost::detail::thr ead_data_base> 0002adc0 V typeinfo name for boost::detail::sp_counted_impl_p<boost::exception_d etail::clone_impl<boost::exception_detail::bad_alloc_> > 0002ad60 V typeinfo name for boost::detail::sp_counted_impl_p<boost::exception_d etail::clone_impl<boost::exception_detail::bad_exception_> > 000296f1 V typeinfo name for boost::system::system_error I see this after having stripped the binary. Is there any way to get rid of these? Do I need to build Boost with some special cxxflags? Kind regards, Philip Bennefall

3 6

[predef] FYI..
by Rene Rivera 01 Aug '13

01 Aug '13

FYI.. to those that care.. I checked in changes to SVN to inject the Predef library into Boost. I say inject because the source is not actually in the SVN repo, it's external and still in github. But is being brought in through their SVN interface. Some testers have already runs the tests for it.. And at some point to be determined with some coordination with the community I will switch the "boost/detail/endian.hpp" header to point to the Predef compatibility equivalent... I suspect at the earliest one more week for that assuming no problems surface. Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

6 10

[predef] A few questions
by Andrey Semashev 01 Aug '13

01 Aug '13

Hi, I have a few questions/nitpicks regarding Boost.Predef: - I see that all headers have extension .h. Why is it not .hpp, like with the rest of Boost? It this intentional? - There is a tab in predef/version_number.h. There are also tabs in tests. - There are __SunOS_5_10, __SunOS_5_11 and similar macros defined on Solaris, which allow to detect OS version. These are not always available but I think SunPro defines them. Could these macros be used to select the proper OS version? - If I'm not mistaken, BOOST_COMP_GNUC and BOOST_COMP_MSVC will get defined not only for the real GCC and MSVC but also for pretenders. Is this intentional? If so, could we have special macros to detect these particular compilers? Boost.Config defines BOOST_MSVC and BOOST_GCC for this purpose. - There is considerable overlap with Boost.Config. Is there any plan to reduce the duplication? Maybe move some things from Boost.Config to Boost.Predef?

3 2

[boost.thread] Trouble building with MinGw 4.7.0
by Philip Bennefall 01 Aug '13

01 Aug '13

Hi all, Up until now I have been developing exclusively with VC++ 2010, and there my project builds just fine and without warnings. However, I am also planning to target Unix so I figured that a first step would be to make sure my project builds with MinGw. I set up my path environment variable to include the location of the MinGw 4.7.0 bin directory, and I built Boost with the following parameters: b2 variant=release link=static runtime-link=static threading=multi toolset=gcc Everything seems to be working fine (stage/lib contains all the .a files that I would expect). However, when I attempt to build my program I get tons of errors like the following: myprog_main.o:myprog_main.cpp:(.text+0x28ef): undefined reference to `__imp___ZN5boost6thread9interruptEv' myprog_main.o:myprog_main.cpp:(.text+0x294f): undefined reference to `__imp___ZNK5boost6thread6get_idEv' myprog_main.o:myprog_main.cpp:(.text+0x295d): undefined reference to `__imp___ZN5boost11this_thread6get_idEv' myprog_main.o:myprog_main.cpp:(.text+0x2973): undefined reference to `__imp___ZN5boost6thread13join_noexceptEv' myprog_main.o:myprog_main.cpp:(.text+0x2981): undefined reference to `__imp___ZN5boost6thread6detachEv' myprog_main.o:myprog_main.cpp:(.text+0x4600): undefined reference to `__imp___ZN5boost11this_thread18interruptible_waitEPvNS_6detail7timeoutE' myprog_main.o:myprog_main.cpp:(.text+0x49c2): undefined reference to `__imp___ZN5boost11this_thread18interruptible_waitEPvNS_6detail7timeoutE' myprog_main.o:myprog_main.cpp:(.text+0x667e): undefined reference to `__imp___ZN5boost11this_thread18interruptible_waitEPvNS_6detail7timeoutE' myprog_main.o:myprog_main.cpp:(.text+0x90a9): undefined reference to `__imp___ZN5boost6thread21start_thread_noexceptEv' myprog_main.o:myprog_main.cpp:(.text+0x9134): undefined reference to `__imp___ZN5boost6thread21start_thread_noexceptEv' myprog_main.o:myprog_main.cpp:(.text+0x917e): undefined reference to `__imp___ZN5boost6thread9interruptEv' myprog_main.o:myprog_main.cpp:(.text$_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvPFvPN5myprog5themeEENS2_5list1INS2_5valueIS6_EEEEEEED1Ev[boost::detail::thread_data<boost::_bi::bind_t<void, void (*)(myprog::theme*), boost::_bi::list1<boost::_bi::value<myprog::theme*> > > >::~thread_data()]+0x7): undefined reference to `__imp___ZN5boost6detail16thread_data_baseD2Ev' myprog_main.o:myprog_main.cpp:(.text$_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvPFvPN5myprog5themeEENS2_5list1INS2_5valueIS6_EEEEEEED0Ev[boost::detail::thread_data<boost::_bi::bind_t<void, void (*)(myprog::theme*), boost::_bi::list1<boost::_bi::value<myprog::theme*> > > >::~thread_data()]+0xe): undefined reference to `__imp___ZN5boost6detail16thread_data_baseD2Ev' myprog_main.o:myprog_main.cpp:(.text$_ZN5boost6threadD1Ev[boost::thread::~thread()]+0x9): undefined reference to `__imp___ZN5boost6thread6detachEv' Etc... I tried to specify -DBOOST_NO_LIB and add all the libraries manually, but no luck. Then I thought that maybe there's a problem with the fact that there are spaces in some of my directory names, so I copied the relevant .a files to the same directory as the program itself but still with no success. At this point, I'm swamped. I have managed to compile MinGw programs in the past that used Boost Thread, so I have no idea why it is not working with this version of Boost. Any suggestions would be highly appreciated. Kind regards, Philip Bennefall

2 5

Re: [boost] [multimethods] Proposal: Open Multi-Methods
by Daryle Walker 01 Aug '13

01 Aug '13

//================================================================= From: Jean-Louis Leroy Sent: ‎Saturday‎, ‎July‎ ‎27‎, ‎2013 ‎8‎:‎26‎ ‎PM I am working on library that pretty much implements what Pirkelbauer, Solodkyy and Stroustrup describe in their paper "Open Multi-Methods for C++" - although there are some divergences. I have posted it on GitHub: https://github.com/jll63/multimethods. Please examine the files in the "examples" directory to get an idea of how to use it. [SNIP] The library is essentially feature complete (if anything ever is). I am now going to work on the documentation, a build system, some clean up and compatibility (I tested it only with g++ 4.7.2 only so far). Is there interest in the Boost community for this stuff? If yes, I will adapt it to the guidelines and submit it for formal review. Of course, suggestions are welcome. //================================================================= Are virtual base classes supported? Maybe “virtual_” should be renamed to “virtualize” or “virtualized,” to avoid having a trailing underscore in a non-member name. A good way to document is to write a Doxygen comment as you write your class, function, or macro prototype. It makes you have to think about what the public side of your code has to do. But looking at your “next.cpp” example, you should start with documenting the “selector,” “virtual_,” “MM_CLASS,” “MM_INIT,” “MULTIMETHOD,” “BEGIN_METHOD,” “END_METHOD,” and “initialize” items. Anything in your implementation classes that don’t have to be seen by public code can be make private. Non-public types can go in a detail namespace. Daryle W.

3 2

[boost thread] Catching interrupted exception?
by Philip Bennefall 31 Jul '13

31 Jul '13

Hi all, I have a quick question regarding the interruption of Boost threads. I am making fairly heavy use of the interrupt method call of the thread class, and I am wondering whether I should be catching the boost::thread_interrupted exception from within my thread function? I currently do not and my program runs fine, but I am wondering whether this is defined behavior or whether I should always be catching the exception and returning from the function inside the handler? Kind regards, Philip Bennefall

2 2