Re: [Boost-bugs] [Boost C++ Libraries] #2100: thread fails to compile with -fno-exceptions

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2100: thread fails to compile with -fno-exceptions
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-11-23 14:35:14

#2100: thread fails to compile with -fno-exceptions
---------------------------------+------------------------------------------
 Reporter:  brbarret@…           |       Owner:  anthonyw
     Type:  Bugs                 |      Status:  new     
Milestone:  Boost 1.40.0         |   Component:  thread  
  Version:  Boost 1.35.0         |    Severity:  Problem 
 Keywords:                       |  
---------------------------------+------------------------------------------

Comment(by anonymous):

 Replying to [comment:6 viboes]:
 > I inspected the patch before posting and I know also
 boost::throw_exception. Do you mean that the application building with
 -fno-exceptions will be happy to abort instead of throwing an exception?

 Yes. In GCC's standard library using -fno-exceptions will turn any throw
 into an abort(), see
 http://gcc.gnu.org/onlinedocs/libstdc++/manual/using_exceptions.html#intro.using.exception.no


 So if a user is using GCC and compiling with -fno-exceptions then they
 *already* expect exceptions to cause the program to abort.  The OP's patch
 does not suggest changing the API to use return codes, it just allows the
 user to decide what should happen when exceptions are disabled.  Which is
 supported in other parts of Boost and seems like a reasonable request to
 me.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/2100#comment:7>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.