Re: [Bug-gnulib] Re: requirements of 'unlocked-io' module

[Bruno Haible]

Paul Eggert wrote:
> Perhaps the simplest fix for now is to add a new macro
> gl_FUNC_GLIBC_UNLOCKED_IO that defaults to not using unlocked io, but
> uses unlocked io if it is given an argument of 1.  The existing
> jm_FUNC_GLIBC_UNLOCKED_IO would be equivalent to
> gl_FUNC_GLIBC_UNLOCKED_IO(1).  This would be a signal to the user that
> one has to decide whether any app might be multithreaded.

And what do you do about the macros for the modules that depend on
'unlocked-io'? (argmatch, closeout, error, exclude, fatal, getdate,
getline, getndelim2, getpass, getusershell, linebuffer, md5, mountlist,
etc. etc.) Do they all get an optional argument denoting multithread-safety?
Urgh.

I think this issue is a documentation question: The customizability is already
there in unlocked-io.h. What we need is to start gathering maintainer
documentation that doesn't belong in the .h or .c file. I suggest to add a new
tag "Notes" to the files in the modules/ directory. (The .texi file in doc/
should IMO contain user / reference documentation, not maintainer
documentation.) What do you think?

Bruno