Eric Blake wrote: > Next I'm wondering if we should add a module which invokes > gl_DISABLE_THREADS, as well as pulls in the unlocked-io module, for the > benefit of projects that are known to be single-threaded, as it is > slightly easier to add a module to the list of imports than it is to > modify configure.ac to manually invoke gl_DISABLE_THREADS.
I don't think this would be a good idea, precisely because it is so easy, and because importing extra modules from gnulib otherwise is a no-brainer. But the decision whether to use gl_DISABLE_THREADS must be a conscious one. For example, if coreutils/src/sort.c becomes multithreaded, coreutils cannot use this macro. Bruno
