From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: 1.6.8 release candidate 0 available for testing.
Date: Mon, 24 Oct 2005 08:27:16 +1000 [thread overview]
Message-ID: <878xwj50or.fsf@zip.com.au> (raw)
In-Reply-To: <rmiach58lyc.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "19 Oct 2005 13:18:19 -0400")
Greg Troxel <gdt@ir.bbn.com> writes:
>
> 1) declare the Scheme proc strftime has extended semantics beyond C99,
> document them,
Straight "pass through" to libc sounds good to me.
> and make the implementation set TZ before calling
> strftime (perhaps unless an implementation which guarantees to read
> tm_zone is detected).
That might be slow. I notice what localtime does changing TZ is a
noticable slowdown with glibc. (It re-reads the timezone file(s) on
every TZ change.)
I wonder if munging the global tzname[] variable would be enough. Bad
for multi-threading, but we've got issues with that in the time funcs
already.
> Perhaps don't set
> the non-C99 fields in what is used for the libc call to avoid
> nonportable expectations.
I wouldn't deliberately break something just because it's not
portable.
> The meta-issue I see here is about guile providing consistent behavior
> on all platforms.
Though I see your point.
PS. I added "man 3 strftime" to the manual.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-23 22:27 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 [this message]
2005-10-25 1:29 ` Greg Troxel
2005-10-31 23:41 ` Kevin Ryde
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=878xwj50or.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).