This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC PATCH 51/52] Y2038: add RPC functions

From: Paul Eggert <eggert at cs dot ucla dot edu>
To: Albert ARIBAUD <albert dot aribaud at 3adev dot fr>
Cc: libc-alpha at sourceware dot org
Date: Sun, 10 Sep 2017 23:33:01 -0700
Subject: Re: [RFC PATCH 51/52] Y2038: add RPC functions
Authentication-results: sourceware.org; auth=none
References: <20170907224219.12483-50-albert.aribaud@3adev.fr> <20170908174909.28192-1-albert.aribaud@3adev.fr> <20170908174909.28192-2-albert.aribaud@3adev.fr> <de6ee744-92b4-f464-2bf8-be875c9e6191@cs.ucla.edu> <20170909163728.05fa95ee.albert.aribaud@3adev.fr>

Albert ARIBAUD wrote:

time_t is a signed int, but its negative range is not completely
usable since (time_t)-1 is used as an error status. So should the
TIME_T_MIN limit be LONG_MIN or should it be 0?

Definitely LONG_MIN. Functions like localtime accept -1 as valid input meaning1969-12-31 23:59:59 UTC.

Even for some functions like mktime that return -1 as an error indicator, -1 canalso be a valid (non-error) return value. I help maintain application code thatcan tell the difference between the two seemingly-identical -1s that mktimereturns, so that the time_t range is completely usable there too. Admittedlyit's not an ideal API.

References:
- [RFC PATCH 49/52] Y2038: add function pselect
  - From: Albert ARIBAUD (3ADEV)
- [RFC PATCH 50/52] Y2038: add function select
  - From: Albert ARIBAUD (3ADEV)
- [RFC PATCH 51/52] Y2038: add RPC functions
  - From: Albert ARIBAUD (3ADEV)
- Re: [RFC PATCH 51/52] Y2038: add RPC functions
  - From: Paul Eggert
- Re: [RFC PATCH 51/52] Y2038: add RPC functions
  - From: Albert ARIBAUD

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]