From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org, Rob Browning <rlb@defaultvalue.org>
Subject: Re: 1.6.8 release candidate 0 available for testing.
Date: Wed, 19 Oct 2005 11:34:12 +1000 [thread overview]
Message-ID: <87fyqy8f3f.fsf@zip.com.au> (raw)
In-Reply-To: <rmir7aiy539.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "18 Oct 2005 15:53:30 -0400")
Greg Troxel <gdt@ir.bbn.com> writes:
>
> I didn't find C99 specs for strftime, so I don't know if programs are
> required to set tm_zone before calling strftime.
The bit about %Z is
%Z is replaced by the locale's time zone name or
abbreviation, or by no characters if no time zone is
determinable. [tm_isdst]
which I suppose is because struct tm is speced without tm_zone.
> So, I respectfully suggest that the test is demanding more than one
> can rightfully conclude from the documentation.
You'd think a system with tm_zone should use it, but yes no sense
demanding what doesn't work.
> Perhaps libguile/strftime.c needs to not assume that strftime(3) will examine
> fields not specified by the standard, or perhaps that Scheme strftime
> should define what it does more precisely. A problem here is that
> guile uses a structure which is bigger than C89 says.
Since we initialize tm_zone if it exists we should be safe, but a note
in the docs about what guile tm:zone might or might not do could be in
order.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-19 1:34 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 [this message]
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
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=87fyqy8f3f.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
--cc=rlb@defaultvalue.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).