Getting Current UTC
#9
> probably better to use (...) the number of seconds (optionally including milliseconds0) since  January 1, 1970, at 00:00:00.

Horses for courses. I work with data going back to 1960, so I prefer FILETIME: the number of 100-nanosecond units since the start of January 1, 1601.  PowerTime is based on FILETIME. But if I was a cosmologist working on the age of the universe, even that would not have enough range, and I wouldn't need nanosecond precision.

For the OP's needs, the onlly reason I'd prefer FILETIME is that it is native to the compiler, and Windows uses FILETIME under the hood for everything.
Reply


Messages In This Thread
Getting Current UTC - by Owen_English - 05-30-2025, 06:22 AM
RE: Getting Current UTC - by Kurt Kuzba - 05-30-2025, 11:32 AM
RE: Getting Current UTC - by Owen_English - 05-30-2025, 11:45 AM
RE: Getting Current UTC - by Stuart McLachlan - 08-31-2025, 03:06 AM
RE: Getting Current UTC - by Albert Richheimer - 05-30-2025, 11:54 AM
RE: Getting Current UTC - by Owen_English - 05-30-2025, 11:58 AM
RE: Getting Current UTC - by Dale Yarker - 05-30-2025, 12:09 PM
RE: Getting Current UTC - by George Bleck - 05-30-2025, 10:29 PM
RE: Getting Current UTC - by Eric Pearson - 08-31-2025, 08:19 AM
RE: Getting Current UTC - by Stuart McLachlan - 08-31-2025, 09:04 AM
RE: Getting Current UTC - by Stuart McLachlan - 09-01-2025, 06:06 AM
RE: Getting Current UTC - by Dale Yarker - 09-01-2025, 08:06 AM
RE: Getting Current UTC - by Dale Yarker - 09-01-2025, 10:02 AM
RE: Getting Current UTC - by Stuart McLachlan - 09-01-2025, 10:37 AM
RE: Getting Current UTC - by Stuart McLachlan - 09-03-2025, 06:05 AM

Forum Jump:


Users browsing this thread: 2 Guest(s)