Tony Hoyle wrote:
David J Taylor wrote:
Interesting that I have never seen any of these so-called problems
in my own software! Mind you, all my stuff uses UTC internally -
perhaps that's why!
It depends on how you get UTC. If you're using something like stat()
you will be seeing the problem since your time_t values will be wrong
for half your files (unless you're on FAT32). If you're getting it
from GetFileTime directly from NTFS then it will (probably) be right.
It's precisely because I write software that uses UTC internally that
it's such a big issue - I rely on UTC being a fairly reliable
constant, so that clients across the world are using the same
timebase.. with the Win32 bugs this wasn't true and it kinda broke
stuff. Ancient history though... there are fixed routines dating
back to 2001 - http://www.codeproject.com/datetime/dstbugs.asp
Tony
I use GetSystemTime on Windows to get my UTC. Never seen any problems
with that. If I do use file times anywhere (and I have one routine that
sorts by file timestamp), all the files will be from the same file system,
so the issues don't arise. Perhaps I have been lucky.
David
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
