Jilles Tjoelker wrote, on 24 May 2021: > > On Tue, May 04, 2021 at 01:07:39AM +0200, Bruno Haible via > austin-group-l at The Open Group wrote: > > https://posix.rhansen.org/p/gettext_split > > says (line 92): > > > "The returned string may be invalidated by a subsequent call to > > bind_textdomain_codeset(), bindtextdomain(), setlocale(), > > textdomain(), or uselocale()." > [...] > > > I think that specifying gettext() to be so restricted is not useful. > > It would make more sense to allow concurrent uselocale() calls. > > > Proposed wording: > > > "The returned string may be invalidated by a subsequent call to > > bind_textdomain_codeset(), bindtextdomain(), setlocale(), > > or textdomain()." > > This may be a bit too weak. Now the implementation can never free a > string that was returned by a gettext call on a thread with uselocale() > active, [...]
In yesterday's teleconference we updated the proposed text to say that the returned string may be invalidated by a subsequent call to uselocale() in the same thread (and clarified that for the other functions it's a subsequent call in the same process). -- Geoff Clare <[email protected]> The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
