Re: [Boost-users] [chron] time_point convertible?

Le 17/01/14 16:21, Nat Goodspeed a écrit :

On Fri, Jan 17, 2014 at 9:39 AM, Agustín K-ballo Bergé wrote:

...

Your API exposes both time_point and duration, that doesn't mean you have to use them internally. What (I think) Bjorn is pointing at is that durations are clock agnostic, so you should build your internal implementation using the most precise duration you are willing to support instead of using a clock. You can then turn any time_point or duration into the specific duration you deal with internally, right at the outermost layer.

Vicente (author of Boost.Chrono) has already explained this on the thread where he requests this functionality to be present. Refer to that thread for more detail. I think you just explained it more clearly, at least for me. I now understand better the referenced discussion.

Thanks Agustin for clarifying my concern. Nat, glad to see you understand now what I was requesting. Hoping Oliver would understand it also, Vicente