I was wondering if msecs will get the documented status one day, and maybe be part of functions like report.
Oh, and if will also evolve in nsecs, so to support the full time resolution of NTFS
You know which buttons to push...You'd be the first to implement it...
Sure! Even down to the 100-nanoseconds! Sorting by time is always maximally precise, independently of the display. Not my merit but built into the Windows time sorting API.grindax wrote:Very nice. It's comforting to know that that kind of precision is now there if needed. Presumably sorting by timestamp will always take the milliseconds into account even when they're not currently being displayed in the date columns?
admin wrote:Done.![]()
Yes, I think I can do that.Marco wrote:Could datediff() or compare() support milliseconds too? Actually, just one of those would be enough. (I have a little script that picks the three dates of a file and then sets all them to the earliest one. Yep, I'm that paranoid)
PS: I notice that the recent addition of UTC times and milliseconds can introduce new usage possibilities and syntax pitfalls in functions handling dates. I'll do some tests, if you think it's necessary/worth. One for sure tho, timestamp() seems to handle every combination smoothly.
Code: Select all
+ SC report: Now milliseconds are supported. Examples:
echo now("fff");
echo now("yyyy-mm-dd hh:nn:ss.fff");Code: Select all
// modified time test
writefile("test.txt", "test");
echo now("yyyy-mm-dd hh:nn:ss.fff");