Source-Changes-D archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: CVS commit: src/lib/libc/time
On Wed, 17 Apr 2019, Christos Zoulas wrote:
On Apr 18, 10:07am, paul%whooppee.com@localhost (Paul Goyette) wrote:
-- Subject: Re: CVS commit: src/lib/libc/time
| Here's a draft. If there's no objection, I can commit it in a day or
| two.
Put it as part of the documentation and say that it is a bug that there
is no way to get one referencing a particular point in time.
christos
Here's round 2 - let me know if this is acceptable:
Index: tzset.3
===================================================================
RCS file: /cvsroot/src/lib/libc/time/tzset.3,v
retrieving revision 1.39
diff -u -p -r1.39 tzset.3
--- tzset.3 19 Oct 2018 23:05:35 -0000 1.39
+++ tzset.3 18 Apr 2019 03:26:00 -0000
@@ -1,5 +1,5 @@
.\" $NetBSD: tzset.3,v 1.39 2018/10/19 23:05:35 christos Exp $
-.Dd October 19, 2018
+.Dd April 18, 2019
.Dt TZSET 3
.Os
.Sh NAME
@@ -89,6 +89,12 @@ is set to
.Va 1
the call is equivalent to
.Va tzname[1] .
+The return values for both
+.Fn tzgetname
+and
+.Fn tzgmtoff
+correspond to the latest time for which data is available, even if that
+refers to a future time.
Finally, the
.Fn tzgetgmtoff
function acts like
@@ -424,6 +430,13 @@ The
.Fn tzset
function conforms to
.St -p1003.1-88 .
+.Sh BUGS
+Neither the
+.Fn tzgetname
+nor
+.Fn tzgmtoff
+functions have the ability to specify the point in time for which the
+requested data should be returned.
.\" @(#)newtzset.3 8.2
.\" This file is in the public domain, so clarified as of
.\" 2009-05-17 by Arthur David Olson.
+--------------------+--------------------------+-----------------------+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost |
+--------------------+--------------------------+-----------------------+
Home |
Main Index |
Thread Index |
Old Index