GNU bug report logs -
#26329
monotonic time not supplied by current-time
Previous Next
Reported by: Zefram <zefram <at> fysh.org>
Date: Sat, 1 Apr 2017 11:19:01 UTC
Severity: normal
Done: Andy Wingo <wingo <at> igalia.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 26329 in the body.
You can then email your comments to 26329 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guile <at> gnu.org
:
bug#26329
; Package
guile
.
(Sat, 01 Apr 2017 11:19:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Zefram <zefram <at> fysh.org>
:
New bug report received and forwarded. Copy sent to
bug-guile <at> gnu.org
.
(Sat, 01 Apr 2017 11:19:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
The SRFI-19 current-time function can return several flavours of the
current time:
scheme@(guile-user)> (use-modules (srfi srfi-19))
scheme@(guile-user)> (current-time time-utc)
$1 = #<time type: time-utc nanosecond: 727666000 second: 1491045256>
scheme@(guile-user)> (current-time time-tai)
$2 = #<time type: time-tai nanosecond: 414752000 second: 1491045294>
scheme@(guile-user)> (current-time time-monotonic)
$3 = #<time type: time-tai nanosecond: 814494000 second: 1491045297>
The last of these three is erroneous: a time structure of type
time-monotonic was requested and must be returned, but instead the
type is time-tai. Although the implementation gives these two time
types numerically identical behaviour, it does treat them as nominally
distinct in other operations:
scheme@(guile-user)> (eqv? time-tai time-monotonic)
$4 = #f
scheme@(guile-user)> (julian-day->time-tai 2450000)
$5 = #<time type: time-tai nanosecond: 0 second: 813240029>
scheme@(guile-user)> (julian-day->time-monotonic 2450000)
$6 = #<time type: time-monotonic nanosecond: 0 second: 813240029>
-zefram
Reply sent
to
Andy Wingo <wingo <at> igalia.com>
:
You have taken responsibility.
(Wed, 19 Apr 2017 13:11:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Zefram <zefram <at> fysh.org>
:
bug acknowledged by developer.
(Wed, 19 Apr 2017 13:11:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 26329-done <at> debbugs.gnu.org (full text, mbox):
On Sat 01 Apr 2017 13:18, Zefram <zefram <at> fysh.org> writes:
> The SRFI-19 current-time function can return several flavours of the
> current time:
>
> scheme@(guile-user)> (use-modules (srfi srfi-19))
> scheme@(guile-user)> (current-time time-utc)
> $1 = #<time type: time-utc nanosecond: 727666000 second: 1491045256>
> scheme@(guile-user)> (current-time time-tai)
> $2 = #<time type: time-tai nanosecond: 414752000 second: 1491045294>
> scheme@(guile-user)> (current-time time-monotonic)
> $3 = #<time type: time-tai nanosecond: 814494000 second: 1491045297>
>
> The last of these three is erroneous: a time structure of type
> time-monotonic was requested and must be returned, but instead the
> type is time-tai.
Thanks for the report; fixed. Patches welcome too.
Andy
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 18 May 2017 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 8 years and 38 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.