From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: nstrftime %c bug w.r.t. time zone
Date: Thu, 8 Feb 2024 23:36:50 -0800 [thread overview]
Message-ID: <d6dad056-46ba-46e5-aefe-6588079042ad@cs.ucla.edu> (raw)
In-Reply-To: <2383643.yKrmzQ4Hd0@nimes>
On 2024-02-08 03:50, Bruno Haible wrote:
> This patch provides a workaround, and thus removes the test-nstrftime-2.sh
> failure at test-nstrftime.h:421.
I was thinking of something a bit more general: temporarily set the time
zone before calling the underlying strftime, and reset it afterwards.
This of course won't work in a multithreaded system without some
locking, but we can either add the locking or not bother.
time_rz.c already does this sort of thing, and I suppose it could export
its secrets to nstrftime.c.
next prev parent reply other threads:[~2024-02-09 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 0:04 nstrftime %c bug w.r.t. time zone Bruno Haible
2024-02-08 11:50 ` Bruno Haible
2024-02-08 13:55 ` Bruno Haible
2024-02-09 7:36 ` Paul Eggert [this message]
2024-02-09 10:10 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6dad056-46ba-46e5-aefe-6588079042ad@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@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).