[omniORB] omniORB: Status of 2038 compatibility with time_t
Duncan Grisby
duncan at grisby.org
Tue Jun 24 09:11:09 UTC 2025
On Mon, 2025-06-23 at 00:02 +0200, Thomas Braun via omniORB-list wrote:
> While working on some code involving omni_thread::get_time() I was
> wondering if omniORB does already support times beyond 2038?
On 64 bit Unix / Linux, unsigned long is 64 bits, so there is no
concern at all.
On 32 bit platforms, plus all versions of Windows, unsigned long is 32
bits, but it is unsigned, so it does not have a 2038 problem — that
applies to signed 32 bits. With unsigned, the limit is 2106.
At some point, omnithread's time handling should be changed to use 64
bits on all platforms, but that would of course be a binary
incompatible change that requires a major release. It is not going to
be a problem in 2038, so there is no pressing need for it.
Duncan.
--
Duncan Grisby <duncan at grisby.org>
More information about the omniORB-list
mailing list