forked from latticeware/Cytoplasm
Update documentation on UtilServerTs().
This commit is contained in:
parent
bcfab52f09
commit
4e58b41049
1 changed files with 8 additions and 8 deletions
|
@ -52,14 +52,14 @@
|
||||||
* and time_t, and converts it to a single number, which is then
|
* and time_t, and converts it to a single number, which is then
|
||||||
* returned to the caller.
|
* returned to the caller.
|
||||||
* .Pp
|
* .Pp
|
||||||
* A note on the 2038 problem: as long as sizeof(long) >= 8, that is,
|
* A note on the 2038 problem: as long as sizeof(time_t) >= 8, that is,
|
||||||
* as long as the long data type is 64 bits or more, then everything
|
* as long as the time_t type is 64 bits or more, then everything
|
||||||
* should be fine. On most, if not, all, 64-bit systems, long is 64
|
* should be fine. On most, if not, all, 64-bit systems, time_t is 64
|
||||||
* bits. I would expect Cytoplasm to break for 32 bit systems
|
* bits. time_t is promoted to a 64-bit integer before it is converted
|
||||||
* eventually, but we should have a ways to go before that happens.
|
* to milliseconds, so there is no risk of overflue due to the
|
||||||
* I didn't want to try to hack together some system to store larger
|
* multiplication by 1000. However, if time_t is only 32 bits, it will
|
||||||
* numbers than the architecture supports. But we can always
|
* overflow before it even gets to this function, which will cause this
|
||||||
* re-evaluate over the next few years.
|
* function to produce unexpected results.
|
||||||
*/
|
*/
|
||||||
extern UInt64 UtilServerTs(void);
|
extern UInt64 UtilServerTs(void);
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue