Paul Eggert wrote:
> * The calling code (though not gnulib) must assume support for
> C99 compound literals.
If we go this route, then I'd be in favour of letting gnulib-tool check
that, by default, it does not include code that assumes C99. This means:
- Modules should have an optional attribute "requires-c99",
- gnulib-tool should, by default, give an error when such a module is used.
- gnulib-tool should have an option --assume-c99 that silences this error.
- gnulib-tool should have options --with/--without-c99-tests that allows
control over whether to include unit tests that require C99 (needed
because 'hash-tests' will require C99 but 'hash' won't).
Bruno
