diff options
| author | normal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2018-08-27 08:48:49 +0000 |
|---|---|---|
| committer | normal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2018-08-27 08:48:49 +0000 |
| commit | d1ccd0afbb962bef08161436c90b62074127335c (patch) | |
| tree | 6b3a8a9bdcb06281d062d3c9e98cfe13163d497a /hrtime.h | |
| parent | eba9c8b89fcf5ff541951b60b541e60f74729e35 (diff) | |
| download | ruby-d1ccd0afbb962bef08161436c90b62074127335c.tar.gz | |
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
Diffstat (limited to 'hrtime.h')
| -rw-r--r-- | hrtime.h | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -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 |