Re: time op inconsistent on Win32

Ron Blaschke wrote: Jonathan Worthington wrote: I've just been looking at the time op, and what it returns is somewhat platform specific. * On Win32, it's the number of seconds since January 1, 1601 If I remember correctly, some parts of Windows use 100ns ticks since 1601 to represent time.

Re: time op inconsistent on Win32

On Thu, Aug 7, 2008 at 12:40 PM, Ron Blaschke <[EMAIL PROTECTED]> wrote: > Jonathan Worthington wrote: >> >> Hi, >> >> I've just been looking at the time op, and what it returns is somewhat >> platform specific. >> >> * On Win32, it's the number of seconds since January 1, 1601 > > If I remember co

Re: time op inconsistent on Win32

Jonathan Worthington wrote: Hi, I've just been looking at the time op, and what it returns is somewhat platform specific. * On Win32, it's the number of seconds since January 1, 1601 If I remember correctly, some parts of Windows use 100ns ticks since 1601 to represent time. Not sure if c

time op inconsistent on Win32

Hi, I've just been looking at the time op, and what it returns is somewhat platform specific. * On Win32, it's the number of seconds since January 1, 1601 * In other codepaths, it appears to be the number of seconds since January 1, 1970. I'm thinking we should correct the Win32 version to