aboutsummaryrefslogtreecommitdiffstats
path: root/erts/doc/src/erlang.xml
diff options
context:
space:
mode:
authorRickard Green <[email protected]>2015-03-24 10:27:20 +0100
committerRickard Green <[email protected]>2015-03-24 10:27:20 +0100
commit052695858c07477db480d25d2d858540088d04c3 (patch)
tree1f7d47571b0fbfde208da3ccd3bb4793bf6a5049 /erts/doc/src/erlang.xml
parent18464e275987eaa69c627b1a2784a9deeb216c03 (diff)
downloadotp-052695858c07477db480d25d2d858540088d04c3.tar.gz
otp-052695858c07477db480d25d2d858540088d04c3.tar.bz2
otp-052695858c07477db480d25d2d858540088d04c3.zip
Documentation adjustments
Diffstat (limited to 'erts/doc/src/erlang.xml')
-rw-r--r--erts/doc/src/erlang.xml33
1 files changed, 22 insertions, 11 deletions
diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml
index 98c0ef5f81..7cb417ac92 100644
--- a/erts/doc/src/erlang.xml
+++ b/erts/doc/src/erlang.xml
@@ -110,10 +110,17 @@
<note>
<p>The value of the <c>native</c> time unit gives
you more or less no information at all about the
- quality of time values. It sets an upper bound for
- the resolution as well as for the precision, but it
- gives absolutely no information at all about the
- accuracy.</p>
+ quality of time values. It sets a limit for
+ the
+ <seealso marker="time_correction#Time_Resolution">resolution</seealso>
+ as well as for the
+ <seealso marker="time_correction#Time_Precision">precision</seealso>
+ of time values,
+ but it gives absolutely no information at all about the
+ <seealso marker="time_correction#Time_Accuracy">accuracy</seealso>
+ of time values. The resolution of the <c>native</c> time
+ unit and the resolution of time values may differ
+ significantly.</p>
</note>
</item>
@@ -6435,18 +6442,22 @@ ok
<c>Function</c>.</p></item>
<tag><c>{resolution, OsMonotonicTimeResolution}</c></tag>
- <item><p>Highest possible resolution of current
- OS monotonic time source as parts per second. If
- no resolution information can be retreived from
- the OS, <c>OsMonotonicTimeResolution</c> will be
+ <item><p>Highest possible
+ <seealso marker="time_correction#Time_Resolution">resolution</seealso>
+ of current OS monotonic time source as parts per
+ second. If no resolution information can be retreived
+ from the OS, <c>OsMonotonicTimeResolution</c> will be
set to the resolution of the time unit of
<c>Function</c>s return value. That is, the actual
resolution may be lower than
<c>OsMonotonicTimeResolution</c>. Also note that
the resolution does not say anything about the
- accuracy, and that the precision might not align
- with the resolution. You do, however, know that the
- precision won't be higher than
+ <seealso marker="time_correction#Time_Accuracy">accuracy</seealso>,
+ and that the
+ <seealso marker="time_correction#Time_Precision">precision</seealso>
+ might not align with the resolution. You do,
+ however, know that the precision won't be
+ better than
<c>OsMonotonicTimeResolution</c>.</p></item>
<tag><c>{extended, Extended}</c></tag>