iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 418: Remove duplicate definitions

This commit is contained in:
Victor Stinner 2012-04-12 01:12:42 +02:00
parent 80391681f6
commit 976aae2d30
1 changed files with 0 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
pep-0418.txt
View File

@ -365,43 +365,6 @@ Glossary
<real time>; unfortunately, wall time is itself ambiguous. <real time>; unfortunately, wall time is itself ambiguous.
Resolution
----------
The resolution is the smallest difference between two timestamps supported by
the format used by the clock. For example, clock_gettime() uses a timespec
structure which has two integer fields, tv_sec and tv_nsec, so the resolution
is 1 nanosecond.
Precision
---------
The precision is the effective smallest difference between two timestamps of the
clock. It does not reflect the stability the clock rate. For example,
QueryPerformanceCounter() has a good precision but is known to not have a steady
rate.
Monotonic
---------
A monotonic clock cannot go backward. It may give the same value for two close
reads depending on the clock resolution.
On Linux, CLOCK_MONOTONIC is a monotonic clock but its rate is adjusted by NTP.
Steady
------
A steady clock is a clock with a stable rate.
The `C++ Timeout Specification
<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3128.html>`_ uses the
following definition: "Objects of class steady_clock represent clocks for which
values of time_point advance at a steady rate relative to real time. That is,
the clock may not be adjusted."
Hardware clocks Hardware clocks
=============== ===============