Re: warn-on-use preview, v2

2010-01-11 Thread Eric Blake
Eric Blake byu.net> writes: > Here's spin two of the patch. It turns out that doing one shell loop per > header also allows us to fold in platform-specific inclusion requirements. > ... > Some of our unit tests never use large files, so rather than drag > in a dependency on fseeko, they should

Re: warn-on-use preview, v2

2010-01-11 Thread Eric Blake
According to Bruno Haible on 1/9/2010 8:53 AM: > Eric Blake wrote: >> Here's spin two of the patch. > >> [PATCH 1/4] warn-on-use: new module >> ... >> + supported by the compiler. If the compiler does not support this >> + feature, the macro expands to an unused typedef declaration. > > It's

Re: warn-on-use preview, v2

2010-01-09 Thread Bruno Haible
Eric Blake wrote: > Here's spin two of the patch. > [PATCH 1/4] warn-on-use: new module > ... > + supported by the compiler. If the compiler does not support this > + feature, the macro expands to an unused typedef declaration. It's now an 'extern' declaration, so I would change "unused type

Re: warn-on-use preview, v2

2010-01-04 Thread Eric Blake
According to Eric Blake on 1/1/2010 7:24 AM: >> I would prefer an implementation where the expansion of >> gl_WARN_ON_USE_PREPARE([locale.h], [setlocale]) >> does not depend on other invocations of gl_WARN_ON_USE_PREPARE, even if it >> leads to a larger 'configure' file. > > OK, I'll work on ref