summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authornormal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-08-27 08:48:49 +0000
committernormal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-08-27 08:48:49 +0000
commit3a83ba90c35833bab757998def36cfe872dec461 (patch)
tree6b3a8a9bdcb06281d062d3c9e98cfe13163d497a
parent50840311decf32239980026ee8b3778469556353 (diff)
hrtime.h: add note explaining current use of uint64_t [ci skip]
[ruby-core:88678] git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64554 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-rw-r--r--hrtime.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/hrtime.h b/hrtime.h
index 1685ed8..bf606d5 100644
--- a/hrtime.h
+++ b/hrtime.h
@@ -8,7 +8,8 @@
/*
* Hi-res monotonic clock. It is currently nsec resolution, which has over
- * 500 years of range (unsigned).
+ * 500 years of range (with an unsigned 64-bit integer). Developers
+ * targeting small systems may try 32-bit and low-resolution (milliseconds).
*
* TBD: Is nsec even necessary? usec resolution seems enough for userspace
* and it'll be suitable for use with devices lasting over 500,000 years