Alejandro Colomar wrote:
> > Hmm. Maybe we could include these functions in the string-h module?
>
> Or maybe a more-strings module, that has more string APIs.
> But I'd use a generic name that allows us adding more functions.
No, neither of these two proposals fits the Gnulib requirements and habits.
20 years of Gnulib development have shown that
* It is important to distinguish a module that provides a .h file
from a module that provides a .h file and many functions.
(Examples: 'threads' vs. 'threads-h'.)
The only exception are .h files that define only inline functions
(examples: 'byteswap', 'endian').
* Packages that use Gnulib don't want to compile lots of unwanted
code. Therefore a module whose purpose is to add other functions
later-on is a non-starter.
Paul did this right: One new module for one (or two) new functions.
Bruno
