Re: tzalloc (was: Re: parse-datetime test failure on NetBSD)

[Paul Eggert]

On 3/14/21 11:33 AM, Bruno Haible wrote:
> A close term is "multithread-safe". The API could be implemented in a
> multithread-safe way, but time_rz.c is not multithread-safe, due to the
> function 'change_env'.
>
> It is planned to provide a multithread-safe implementation at some point?

My plan has been to add them eventually to glibc, where they would be 
multithread-safe. It'd be nice to also make them multithread-safe in 
Gnulib, so long as that doesn't make them harder to use with existing 
apps, all of which currently use these functions only in a single thread 
(which is why this is low priority). The only platform I know that 
currently has them is NetBSD, where I believe they're multithread-safe.

I took the word "reentrant" from the "_r" suffix, which as you note is a 
bit of a misnomer here (though a widely used misnomer...).