From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: 1.6.8 release candidate 0 available for testing.
Date: Tue, 01 Nov 2005 10:41:08 +1100 [thread overview]
Message-ID: <87acgpp84r.fsf@zip.com.au> (raw)
In-Reply-To: rmi1x2ajse5.fsf@fnord.ir.bbn.com
Greg Troxel <gdt@ir.bbn.com> writes:
>
> I realize this is a tough call,
I kicked it into touch, by adding this to the manual
Note that `%Z' might print the `tm:zone' in TM or it might print
just the current zone (`tzset' above). A GNU system prints
`tm:zone', a strict C99 system like NetBSD prints the current
zone. Perhaps in the future Guile will try to get `tm:zone' used
always.
and this comment as a reminder
@c
@c The issue in the above is not just whether tm_zone exists in
@c struct tm, but whether libc feels it should read it. Being a
@c non-C99 field, a strict C99 program won't know to set it, quite
@c likely leaving garbage there. NetBSD, which has the field,
@c therefore takes the view that it mustn't read it. See the PR
@c about this at
@c
@c http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=21722
@c
@c Uniformly making tm:zone used on all systems (all those which have
@c %Z at all of course) might be nice (either mung TZ and tzset, or
@c mung tzname[]). On the other hand it would make us do more than
@c C99 says, and we really don't want to get intimate with the gory
@c details of libc time funcs, no more than can be helped.
@c
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-31 23:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 20:55 1.6.8 release candidate 0 available for testing Rob Browning
2005-10-16 21:02 ` Greg Troxel
2005-10-16 22:38 ` Kevin Ryde
2005-10-18 19:53 ` Greg Troxel
2005-10-19 1:27 ` Kevin Ryde
2005-10-19 17:10 ` Greg Troxel
2005-10-20 7:32 ` Ludovic Courtès
2005-10-19 1:34 ` Kevin Ryde
2005-10-19 17:18 ` Greg Troxel
2005-10-23 22:27 ` Kevin Ryde
2005-10-25 1:29 ` Greg Troxel
2005-10-31 23:41 ` Kevin Ryde [this message]
2005-10-23 22:41 ` Kevin Ryde
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=87acgpp84r.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).