Re: POSIX gettext(): multithread-safe or not?

2022-05-24 Thread Bruno Haible via austin-group-l at The Open Group
Thank you for the reply. https://posix.rhansen.org/p/gettext_draft Line 357 Geoff Clare wrote: > However, we have rearranged the wording in a way that > we hope makes it clearer it is a requirement on implementations. Thank you; it is clearer now. It would be even clearer if there was a

Re: POSIX gettext(): multithread-safe or not?

2022-05-24 Thread Geoff Clare via austin-group-l at The Open Group
Bruno Haible wrote, on 12 May 2022: > > https://posix.rhansen.org/p/gettext_draft > Line 357 > > "The returned string shall not be ... invalidated by a subsequent call > to a gettext family function." This was discussed in yesterday's call. > It is not clear whether this sentence is an

POSIX gettext(): multithread-safe or not?

2022-05-11 Thread Bruno Haible via austin-group-l at The Open Group
https://posix.rhansen.org/p/gettext_draft Line 357 "The returned string shall not be ... invalidated by a subsequent call to a gettext family function." It is not clear whether this sentence is an assertion (regarding how the gettext() implementation behaves) or a requirement/restriction w.r.t.