It might be better to put the OS compatibility code in the existing
Process.clock_gettime implementation
Not sure. It is not same as clock_gettime, which accepts parameters and such, and it is not clock_gettime across operating systems.
Also, the point of this patch is to enable access to uniform monotonic clock, so that you don't need to check for OS, what clock you want etc. Process.clock_gettime is simply method exposure, and I would think most people would not appreciate that on OS/X or Windows it does something completely different.
It might be better to put the OS compatibility code in the existing
Process.clock_gettime implementation
Not sure. It is not same as clock_gettime, which accepts parameters and such, and it is not clock_gettime across operating systems.
Also, the point of this patch is to enable access to uniform monotonic clock, so that you don't need to check for OS, what clock you want etc. Process.clock_gettime is simply method exposure, and I would think most people would not appreciate that on OS/X or Windows it does something completely different.
Process.clock_gettime already have compatibility layer for OS X and Windows.
Therefore Process.clock_gettime(Process::CLOCK_MONOTONIC) is portable
It might be better to put the OS compatibility code in the existing
Process.clock_gettime implementation
Not sure. It is not same as clock_gettime, which accepts parameters and such, and it is not clock_gettime across operating systems.
Also, the point of this patch is to enable access to uniform monotonic clock, so that you don't need to check for OS, what clock you want etc. Process.clock_gettime is simply method exposure, and I would think most people would not appreciate that on OS/X or Windows it does something completely different.
Process.clock_gettime already have compatibility layer for OS X and Windows.
Therefore Process.clock_gettime(Process::CLOCK_MONOTONIC) is portable
So it would indeed seem, although I could not see Win32 listed as supported for CLOCK_MONOTONIC, but this could be just my misunderstanding. Thank you for the fast reply anyways!