Bruno Haible <[EMAIL PROTECTED]> writes:
> Maybe it would be worth renaming the module to 'strftime-gnu', for clarity?
Or maybe even "strftime-gnulib", since it's not even glibc. :-)
That's a reasonable request, but if you don't mind I'd rather put off
renaming until we have a real need to dist
Hi Paul,
> Currently it is far more oriented towards providing GNU extensions.
> In fact, it adds extensions beyond what glibc provides.
Thanks. I'm documenting it as below.
Maybe it would be worth renaming the module to 'strftime-gnu', for clarity?
Bruno
*** doc/functions/strftime.texi 1 May
Bruno Haible <[EMAIL PROTECTED]> writes:
> Jim, Paul, I don't understand whether the 'strftime' module is useful when
> someone only wants a POSIX compliant strftime() function. Does it fix known
> POSIX incompatibilities on some systems, or does it only provide GNU
> extensions?
Currently it is
Eric Blake wrote:
> The creation of both doc/functions/_exit.texi and doc/functions/_Exit.texi
> breaks checkout on case insensitive file systems. We need to come up with an
> alternate name for one of these files.
Ah, right. I rename it to _Exit_C99.texi.
Bruno
Bruno Haible clisp.org> writes:
>
> Like the documentation of the header files, I'm adding a documentation of
> each ISO C 99 or POSIX function to the gnulib documentation.
>
> + * _Exit::
> + * _exit::
The creation of both doc/functions/_exit.texi and doc/functions/_Exit.texi
breaks checkou