[Webkit-unassigned] [Bug 37743] Separate clock time functions used by JavaScript from monotonically increasing time needed elsewhere

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue May 31 15:38:08 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=37743





--- Comment #37 from James Simonsen <simonjam at chromium.org>  2011-05-31 15:38:06 PST ---
(In reply to comment #35)
> (From update of attachment 95495 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=95495&action=review
> 
> > Source/JavaScriptCore/wtf/CurrentTime.h:63
> > +uint64_t currentTickCount();
> 
> It's a little awkward to use a 64-bit integer containing microseconds. What’s the argument against using a double containing seconds for this?

The hope was that having separate types would discourage people from confusing them with the values returned from currentTime.

A double of seconds is just as useful for my purposes though, so I'm happy to switch if you'd like.

> Can we name this monotonicallyIncreasingTim instead of currentTickCount?

Sure, I will upload a patch shortly.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list