Re: [Boost-bugs] [Boost C++ Libraries] #5752: boost::call_once() is unreliable on some platforms

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #5752: boost::call_once() is unreliable on some platforms
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-09-13 19:17:15

#5752: boost::call_once() is unreliable on some platforms
----------------------------------------------------+-----------------------
  Reporter:  Matthew Dempsky <matthew@…>            |       Owner:  viboes  
      Type:  Bugs                                   |      Status:  assigned
 Milestone:  Boost 1.52.0                           |   Component:  thread  
   Version:  Boost 1.47.0                           |    Severity:  Problem 
Resolution:                                         |    Keywords:  once    
----------------------------------------------------+-----------------------

Comment (by viboes):

 Replying to [comment:14 fmhess]:
 > SIG_ATOMIC_MAX actually gets defined by stdint.h/cstdint not csignal so
 it seems like your define should be earlier.  Actually, even then there's
 still a problem since the user might include stdint.h before they include
 the once.hpp, without having {{{__STD_LIMIT_MACROS}}} defined.  In that
 case, SIG_ATOMIC_MAX won't be defined in their code but it will be defined
 in the thread library, leading to incompatible types again.

 It seems then that I can not relay on whether SIG_ATOMIC_MAX is defined or
 not, but I need a value to mean not-a-valid value. Have a suggestion?

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