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-17 21:35:34

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

  * milestone:  Boost 1.52.0 => To Be Determined

Comment:

 Replying to [comment:16 fmhess]:
 > Replying to [comment:15 viboes]:
 > >
 > > 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?
 >
 > How about using a boost::atomic<unsigned long> for the epoch?

 I will try to use it when released. I can not depend on a non released
 library.

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