From: Mark H Weaver <mhw@netris.org>
To: Zefram <zefram@fysh.org>
Cc: 21903@debbugs.gnu.org
Subject: bug#21903: date->string duff ISO 8601 negative years
Date: Sat, 20 Oct 2018 18:33:31 -0400 [thread overview]
Message-ID: <87lg6s2qpw.fsf@netris.org> (raw)
In-Reply-To: <20151113140157.GN13455@fysh.org> (Zefram's message of "Fri, 13 Nov 2015 14:01:57 +0000")
Zefram <zefram@fysh.org> writes:
> The date->string function from (srfi srfi-19), used on ISO 8601 formats
> "~1", "~4" and "~5", for years preceding AD 1, has an off-by-one error:
>
> scheme@(guile-user)> (use-modules (srfi srfi-19))
> scheme@(guile-user)> (date->string (julian-day->date 0 0) "~4")
> $1 = "-4714-11-24T12:00:00Z"
>
> The date in question, the JD epoch, is 24 November 4714 BC (in the
> proleptic Gregorian calendar). In ISO 8601 format, that year is properly
> represented as "-4713", not "-4714", because ISO 8601 uses the AD era
> exclusively. 4714 BC = AD -4713.
I agree that this is definitely a bug, but I'm nervous about deviating
from the SRFI-19 reference implementation, and therefore probably from
most other implementations of SRFI-19, in this way.
I think that this bug should be reported to the SRFI-19 mailing list.
https://srfi.schemers.org/srfi-19/
There have been several other bugs reported and fixed in upstream
SRFI-19 over the years, including some as recently as June 2017, so I'm
hopeful that they will take this bug seriously and issue a fix.
Would you like to report it to them?
Mark
next prev parent reply other threads:[~2018-10-20 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 14:01 bug#21903: date->string duff ISO 8601 negative years Zefram
2017-04-20 0:09 ` Zefram
2018-10-20 22:33 ` Mark H Weaver [this message]
2018-10-21 0:40 ` Mark H Weaver
2018-10-21 4:01 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lg6s2qpw.fsf@netris.org \
--to=mhw@netris.org \
--cc=21903@debbugs.gnu.org \
--cc=zefram@fysh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).