3 ms·
That is what apple initially did. And they dropped the approach because few to none were going to rewrite existing code to add support for non-standard extensi
by masklinn 5y ago
That is what apple initially did.
And they dropped the approach because few to none were going to rewrite existing code to add support for non-standard extensions to fix 40 years out issues. Instead they moved to 64b time_t in 10.7 I think?
And it’s not a new call, dozens of functions touch time_t, plus a few syscalls.
- deleted 5y ago[deleted]
- temac 5y agoSince 10.15 only 64 bits code is supported anyway.
- masklinn 5y ago64b code does not necessarily imply 64b time_t though. If your time_t is an alias for int, it's 32b on anything short of (S)ILP64, which is anything but common. I'm not sure there's been any other than Cray's UNICOS and HAL's Solaris port.