From: Ondrej Zajicek <santiago@crfreenet.org>
To: guile-user@gnu.org
Subject: Re: Leap second bug?
Date: Sun, 8 Jun 2008 21:45:12 +0200 [thread overview]
Message-ID: <20080608194512.GA14504@localhost.localdomain> (raw)
In-Reply-To: <20080607204054.GA7677@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
On Sat, Jun 07, 2008 at 10:40:54PM +0200, Ondrej Zajicek wrote:
> (date->str (time-utc->date (date->time-utc (str->date "01-01-2006"))))
> -> "31-12-2005"
>
> Is is a bug in leap second handling or is it a expected behavior?
I forgot to mention that the problem appears in both
Guile 1.6.8 and Guile 1.8.1 .
--
Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-08 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 20:40 Leap second bug? Ondrej Zajicek
2008-06-08 19:45 ` Ondrej Zajicek [this message]
2008-06-08 22:00 ` Ludovic Courtès
2008-06-09 14:58 ` Greg Troxel
2008-06-09 17:18 ` Keith Wright
2008-06-10 15:15 ` Jon Wilson
2008-06-10 18:26 ` Ludovic Courtès
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=20080608194512.GA14504@localhost.localdomain \
--to=santiago@crfreenet.org \
--cc=guile-user@gnu.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).