From 976aae2d30fd7fe004ac539fcfb01331c4a7c207 Mon Sep 17 00:00:00 2001 From: Victor Stinner Date: Thu, 12 Apr 2012 01:12:42 +0200 Subject: [PATCH] PEP 418: Remove duplicate definitions --- pep-0418.txt | 37 ------------------------------------- 1 file changed, 37 deletions(-) diff --git a/pep-0418.txt b/pep-0418.txt index 6890b16b8..0b992b5c0 100644 --- a/pep-0418.txt +++ b/pep-0418.txt @@ -365,43 +365,6 @@ Glossary ; 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 -`_ 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 ===============