From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: MT-unsafe time modules
Date: Fri, 09 Feb 2024 18:43:27 +0100 [thread overview]
Message-ID: <3755090.VQhiAETyHQ@nimes> (raw)
When a module is under LGPL, it is implicitly advertised as suitable for
libraries. And libraries should be MT-safe (for 20 years already). So,
such modules should be MT-safe.
Looking at the LGPLed time-related modules:
* This one is already MT-safe:
timespec
* These need to be made MT-safe:
strftime-fixes
wcsftime
ctime
localtime
mktime, mktime-internal
timegm
time_r
strptime
time_rz
c-nstrftime, nstrftime
parse-datetime, parse-datetime2
I will try to tackle them, in roughly the given order.
Bruno
next reply other threads:[~2024-02-09 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 17:43 Bruno Haible [this message]
2024-02-09 20:22 ` MT-unsafe time modules Bruno Haible
2024-02-10 11:10 ` Bruno Haible
2024-02-11 12:46 ` localtime on native Windows Bruno Haible
2024-02-13 2:02 ` Paul Eggert
2024-02-18 2:38 ` Bruno Haible
2024-02-18 4:50 ` Paul Eggert
2024-02-18 14:38 ` Bruno Haible
2024-02-18 19:05 ` Paul Eggert
2024-02-11 10:43 ` MT-unsafe time modules 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=3755090.VQhiAETyHQ@nimes \
--to=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).