anonymous — Sat, 15 Mar 2014 04:40:08 GMT

Three obvious glitches in my submission:

1) Sorry about the formatting problems. The initial example should be:

// Assume "io_service" working and running normally
boost::asio::steady_timer timer(io_service);
timer.expires_from_now(std::chrono::hours(24));
timer.async_wait([](const boost::system::error_code& e){});

and the "Super short solution" should be:

{
  const int64_t gcd = boost::math::static_gcd<period_type::num * Den, period_type::den * Num>::value;
  const int64_t num_reduced = num / gcd;
  const int64_t den_reduced = den / gcd;
  return ticks() * num_reduced / den_reduced;
}

Note: I haven't just fixed the formatting, I've included an actual type for the gcd variable.

2) I linked to the wrong function in ffmpeg. An actual example of rescaling while guarding against overflow would be the function av_rescale_rnd here:

http://ffmpeg.org/doxygen/0.6/mathematics_8c-source.html

3) Obviously, I didn't mean "8.64e+13 quadrillion", I meant simply "8.64e+13".

status, severity changed; resolution set

chris_kohlhoff — Mon, 05 May 2014 06:53:30 GMT

status new → closed
resolution → fixed
severity Showstopper → Problem

Fixed on 'develop' in 92a53bd3cc7fdf75b0d2eb5ce68a41993852d5f3.

Merged to 'master' in 4e1e7d731fcc5c0104567856de476f7ce8806d72.

Boost C++ Libraries: Ticket #9778: duration_cast in chrono_time_traits.hpp prone to overflow, stopping io_service

status, severity changed; resolution set