Re: st_birthtime

On 3/6/07, Paul Eggert <[EMAIL PROTECTED]> wrote: "James Youngman" <[EMAIL PROTECTED]> writes: > I see that FreeBSD and NetBSD support st_birthtime. I'm considering > supporting these in findutils. Is there any interest in suporting > (i.e. maintaining if I contribute a patch) this in stat-ti

Re: config.rpath conflict

Simon Josefsson <[EMAIL PROTECTED]> wrote: > Bruno Haible <[EMAIL PROTECTED]> writes: > >>> Any suggestions? >> >> The config.rpath in gnulib is newer than the one from the latest gettext >> release (0.16.1). Therefore I would move build-aux/config.rpath away so >> that autopoint doesn't see it, an

Nanosecond time support in getdate?

I see that getdate.y normally zeroes out the nanoseconds field (e.g. $$.tv_nsec = 0). Is it likely that changing the parser to accept floating-point seconds fields would change the meaning of time specifiers that previously were interpreted differently? It doesn't immediately seem so to me, but

Re: Nanosecond time support in getdate?

"James Youngman" <[EMAIL PROTECTED]> writes: > I see that getdate.y normally zeroes out the nanoseconds field (e.g. > $$.tv_nsec = 0). > > Is it likely that changing the parser to accept floating-point seconds > fields Doesn't getdate already accept fractional seconds? It does start out by zeroi

Re: frexpl, ldexpl declarations

Paul Eggert wrote: > Yes, math.h should declare them as functions. But are you sure it isn't > already doing this somehow? It works for me, with Debian stable: You are right. There was a mistake in my autoconf test. Thanks for the clarifications. So, the frexpl, ldexpl declarations are missing

vasnprintf.m4 simplification

This change causes the "checking for vasnprintf..." test to be executed always. But it makes the callers of the gl_REPLACE_VASNPRINTF macro more maintainable. 2007-03-06 Bruno Haible <[EMAIL PROTECTED]> * m4/vasnprintf.m4 (gl_REPLACE_VASNPRINTF): Test for vasnprintf here. * m4/v

new module 'vsnprintf-posix'

Here is the variant of the 'vsnprintf' module that provides a full POSIX vsnprintf() function. 2007-03-06 Bruno Haible <[EMAIL PROTECTED]> * modules/vsnprintf-posix: New file. * m4/vsnprintf-posix.m4: New file. * m4/vsnprintf.m4 (gl_REPLACE_VSNPRINTF): New macro, extract

new module 'snprintf-posix'

Here's the full POSIX snprintf() replacement. 2007-03-06 Bruno Haible <[EMAIL PROTECTED]> * modules/snprintf-posix: New file. * m4/snprintf-posix.m4: New file. * m4/snprintf.m4 (gl_REPLACE_SNPRINTF): New macro, extracted from gl_FUNC_SNPRINTF. (gl_FUNC_SN

new module 'vsprintf-posix'

Does it require a comment? :-) 2007-03-06 Bruno Haible <[EMAIL PROTECTED]> * modules/vsprintf-posix: New file. * lib/vsprintf.c: New file. * m4/vsprintf-posix.m4: New file. * m4/stdio_h.m4 (gl_STDIO_H_DEFAULTS): Set also GNULIB_VSPRINTF_POSIX, REPLACE_VSP

new module 'sprintf-posix'

Hi, You probably already guessed which module would come next. 2007-03-06 Bruno Haible <[EMAIL PROTECTED]> * modules/sprintf-posix: New file. * lib/sprintf.c: New file. * m4/sprintf-posix.m4: New file. * m4/stdio_h.m4 (gl_STDIO_H_DEFAULTS): Set also GNULIB_SPRIN

Re: new module 'vasnprintf-posix'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 3/4/2007 4:28 PM: > The module vasnprintf-posix defines a vasnprintf() function that supports > POSIX format strings with all frills. > > AC_CHECK_FUNCS([vasnprintf]) > if expr "$gl_cv_func_printf_sizes_c99" : ".*yes"