You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2016/09/06 03:05:20 UTC

[jira] [Commented] (TS-4532) Static type checking for time units

    [ https://issues.apache.org/jira/browse/TS-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466248#comment-15466248 ] 

Alan M. Carroll commented on TS-4532:
-------------------------------------

Forget ``NumericType``, I think ``std::chrono`` is overall more useful. I have [pull request|https://github.com/SolidWallOfCode/trafficserver/pull/1] with a partial conversion to start a discussion.

> Static type checking for time units
> -----------------------------------
>
>                 Key: TS-4532
>                 URL: https://issues.apache.org/jira/browse/TS-4532
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>            Reporter: James Peach
>            Assignee: Alan M. Carroll
>             Fix For: 7.0.0
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Since the various time units {{ink_time_t}}, {{time_t}}, {{ink_hrtime}} are all typedefs of C integral types, it is very hard to ensure that units are being converted and compared correctly.
> Consider wrapping these in trivial classes as part of making the time APIs more straightforward. Alternatively, if we move to {{C++11}} investigate {{std::chrono}} for this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)