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

[bugzilla-daemon at webkit.org]

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


James Simonsen <simonjam at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jamesr at chromium.org,
                   |                            |tonyg at chromium.org




--- Comment #33 from James Simonsen <simonjam at chromium.org>  2011-05-31 15:28:26 PST ---
(In reply to comment #32)
> Personally, I like the approach in bug 60936, where we kept the existing function name for clock time and used a new function name for monotonically increasing time, better than the approach in the pathces here where we change currentTime to mean monotonically increasing time.

Yeah, I'd rather just add the new function and move callers over on a case-by-case basis. We'll also need that lead time to implement monotonic time on all the platforms. I'll resubmit my patch here, since that's the path it was on.

We should add other bugs to track the callers we want to migrate (like timers, for starters) and have them depend on this. This bug seems to be trying to do too much.

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