https://posix.rhansen.org/p/gettext_draft
Line 357
"The returned string may be invalidated by ... a subsequent call to
uselocale() in the same thread, except for calls that only query values."
As explained in my mail from 2021-05-04 [1]
uselocale() is a helper function to implement *_l functi
Bruno Haible wrote, on 12 May 2022:
>
> https://posix.rhansen.org/p/gettext_draft
> Line 357
>
> "The returned string may be invalidated by ... a subsequent call to
> uselocale() in the same thread, except for calls that only query values."
>
> As explained in my mail from 2021-05-04 [1]
>
>
Thank you for the reply.
Geoff Clare wrote:
> > https://posix.rhansen.org/p/gettext_draft
> > Line 357
> > ...
> > If temporarily switching a thread's locale through uselocale()
> > invalidates the gettext functions' results (even if only those from
> > the same thread), it effectively disallows u
Date:Wed, 25 May 2022 02:57:52 +0200
From:"Bruno Haible via austin-group-l at The Open Group"
Message-ID: <5462894.CAdn2TfLgq@omega>
| IMO, it's useful to distinguish bounded and unbounded memory leaks:
| - A _bounded_ memory leak is one where the amount of lea
Bruno Haible wrote, on 25 May 2022:
>
> Geoff Clare wrote:
> > > https://posix.rhansen.org/p/gettext_draft
> > > Line 357
> > > ...
> > > If temporarily switching a thread's locale through uselocale()
> > > invalidates the gettext functions' results (even if only those from
> > > the same thread),
Geoff Clare wrote:
> > I hope this explains it: how gettext() can be implemented in a reasonable
> > way, without limiting the use of uselocale().
>
> In today's teleconference we changed the etherpad text to require that
> uselocale() does not invalidate the returned string.
That's great! Thank
Geoff Clare wrote:
> We believe that all of your comments have now been addressed. ... Once
> you have reviewed this last change, we plan to clean up the document
Thanks for the prompt. I have reviewed the specifications of msgfmt and
xgettext, and sent 7 comments about them.
Bruno
