From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org, Thomas Klausner <tk@giga.or.at>
Subject: Re: tzalloc
Date: Sun, 14 Mar 2021 20:37:56 +0100 [thread overview]
Message-ID: <2904699.0bAd9iXiqA@omega> (raw)
In-Reply-To: <d2f3dd24-5a9b-593a-d394-d9f75332061e@cs.ucla.edu>
Paul Eggert wrote:
> My plan has been to add them eventually to glibc, where they would be
> multithread-safe.
That would be nice, indeed!
Use cases that I can see:
- A server process that talks to several users in different locales and
time zones.
(We have locale_t for several years already, but not yet timezone_t.)
- A multithreaded mail agent that wants to sort mails by date, where
each mail lists its own date in a format that includes the time zone.
Bruno
prev parent reply other threads:[~2021-03-14 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 8:24 parse-datetime test failure on NetBSD Thomas Klausner
2021-03-14 10:42 ` Bruno Haible
2021-03-14 11:05 ` Thomas Klausner
2021-03-14 11:53 ` tzalloc (was: Re: parse-datetime test failure on NetBSD) Bruno Haible
2021-03-14 16:02 ` Paul Eggert
2021-03-14 18:33 ` Bruno Haible
2021-03-14 19:02 ` Paul Eggert
2021-03-14 19:37 ` Bruno Haible [this message]
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=2904699.0bAd9iXiqA@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=tk@giga.or.at \
/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).