[Boost-bugs] [Boost C++ Libraries] #10992: Chrono IO state savers inconsistent with Boost.IO state savers

Subject: [Boost-bugs] [Boost C++ Libraries] #10992: Chrono IO state savers inconsistent with Boost.IO state savers
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2015-02-03 22:12:23

#10992: Chrono IO state savers inconsistent with Boost.IO state savers
-------------------------------------+---------------------
 Reporter:  rkawulak                 |      Owner:  viboes
     Type:  Bugs                     |     Status:  new
Milestone:  To Be Determined         |  Component:  chrono
  Version:  Boost Development Trunk  |   Severity:  Problem
 Keywords:                           |
-------------------------------------+---------------------
 The constructors of Boost.IO state savers taking the second new_value
 argument set the state to the new_value immediately and restore the
 previous state upon destruction. OTOH, the Boost.Chrono IO state savers do
 something different (and arguably unintuitive): they don't alter the state
 upon construction at all and restore the state to new_value rather than
 the previous state upon destruction. The behaviour should be aligned with
 that of Boost.IO to avoid confusion and make it more useful.

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