Re: url's in --help output

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Karl Berry on 1/24/2009 5:10 PM: > printf can fail for reasons like ENOMEM which do not set the ferror > flag and thus are not caught by the close_stdout atexit module, so a > robust program should be checking for failures. >

Re: url's in --help output

printf can fail for reasons like ENOMEM which do not set the ferror flag and thus are not caught by the close_stdout atexit module, so a robust program should be checking for failures. Whoa. I hadn't seen this before. at_exit is not sufficient to check for write errors? What does th

Re: Please do not install a charset.alias file under Mac OS X

Vincent Lefevre wrote: > > > I've just reported a bug against gettext: > > > > > > https://savannah.gnu.org/bugs/index.php?25235 > > > > See my response there. In summary, locales with an encoding other than > > UTF-8 are not supported by MacOS X because filenames MUST be in UTF-8 on > > this p

Re: url's in --help output

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Simon Josefsson on 1/22/2009 3:29 AM: > + > +void > +emit_bug_reporting_address (void) > +{ > + /* TRANSLATORS: The placeholder indicates the bug-reporting address > + for this package. Please add _another line_ saying > + "Repor

Re: mem*/strr*/etc... obsolete warnings

Mike Frysinger wrote: > > What extra information would you find useful here? > > the simple explanation you posted in your e-mail should be in the > documentation. and the modules file should point people to that section of > the documentation so that it shows up in the warning when they run th

improve doc/Makefile

While creating the gnulib documentation, I ran into this TeX error "TeX capacity exceeded" again. Adding a hint about it to the Makefile: 2009-01-24 Bruno Haible * doc/Makefile (%.pdf): Clarify where to find texmf.cnf. (%.dvi): New rule. --- doc/Makefile.orig 2009-01-24 16

Re: include_next with OSF/1 cc

Gary V. Vaughan wrote: > !THE FOLLOWING IS A REGRESSION OVER m4-1.4.12, WHICH COMPILES AND > PASSES ALL TESTS! > alphaev5-dec-osf4.0d-cc55 fails to compile: > cc -std -I. -ieee -O2 -nodtk -msym -readonly_strings -c -o > gl_avltree_oset.o gl_avltree_oset.c > cc: Warning: ///usr/include.dtk/s

Re: strtod error handling

Eric Blake wrote: > > No, other reasons are allowed as well. > > Finish reading that paragraph: > > "...if and only if all those error conditions can always be treated > identically to the error conditions as described in this volume of > POSIX.1-2008. This is a chewing-gum sentence: "can always

Re: upstream regex

Eric Blake wrote: > According to Paolo Bonzini on 1/24/2009 6:20 AM: >>> Actually, Paolo imported some glibc fixes into gnulib within the past >>> month. However, we have had some gnulib fixes which have not been pushed >>> back to glibc. >> I see only dea6f7089df0538e8bc7971dfbdd84e523a79d2a in t

Re: strtod error handling

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 1/24/2009 6:34 AM: > >>> + - In case of other error, return 0 and set errno, for example to EINVAL >>> + or ENOMEM. */ >> I think that POSIX is explicit that the only way to fail strtod() with >> EINVAL is if nothin

Re: strtod error handling

Eric Blake wrote: > > + - If the string does not start with a number at all, return 0 (and > > recall > > + that if ENDPTR != NULL, *ENDPTR is set to NPTR). > POSIX allows (but not requires) strtod() to set errno to EINVAL in this > case. Now for the question: is it useful to the client to

Re: c-strtod: handling of out-of-memory

Hi Jim, > > + If ENDPTR is not NULL, set *ENDPTR to point to the first byte beyond the > > + parsed number or to NPTR if the string does not start with a parseable > > + number. > > Perhaps mention that *ENDPTR is always set? I think this is implicit by the fact that this paragraph comes b

Re: upstream regex

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paolo Bonzini on 1/24/2009 6:20 AM: >> Actually, Paolo imported some glibc fixes into gnulib within the past >> month. However, we have had some gnulib fixes which have not been pushed >> back to glibc. > > I see only dea6f7089df0538e8bc

Re: upstream regex

Eric Blake wrote: > According to Bruno Haible on 1/24/2009 4:31 AM: >> glibc regex and gnulib regex are supposed to be synched (bidirectionally) >> regularly. Paul Eggert did this last time in 2006. It's quite some work >> to do this synch. Maybe it could be easier, now that we are using 'git' >> (

Re: upstream regex

> glibc regex and gnulib regex are supposed to be synched (bidirectionally) > regularly. Paul Eggert did this last time in 2006. It's quite some work > to do this synch. Maybe it could be easier, now that we are using 'git' > (using git branches)? I'll look at relevant gnulib patches. When I ask

Re: test-c-stack2.sh failure on HP-UX

Gary V. Vaughan wrote: > hppa2.0w-hp-hpux11.11-hpc m4 tests pass, gnulib fails: test-c-stack.sh > ./test-c-stack.sh[7]: 1752 Memory fault(coredump) > FAIL: test-c-stack.sh I reproduce this on HP-UX 11.11, without libsigsegv. $ ./test-c-stack ./test-c-stack: program error Segmentation fault (c

Re: upstream regex

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 1/24/2009 4:31 AM: > > glibc regex and gnulib regex are supposed to be synched (bidirectionally) > regularly. Paul Eggert did this last time in 2006. It's quite some work > to do this synch. Maybe it could be easier, now t

Re: c-strtod: handling of out-of-memory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 1/24/2009 3:44 AM: > + Return value: > + - If successful, return the value as a double or 'long double', > + respectively, and don't modify errno. > + - In case of overflow, return ±HUGE_VAL or ±HUGE_VALL, respect

Re: test-mbrtowc4.sh on Solaris 8

Gary V. Vaughan wrote: > sparc-sun-solaris2.8-suncc58 m4 tests pass, gnulib fails: test-mbrtowc4.sh > (m4-1.4.12 everything passes, but there is no test-mbrtowc4.sh) On a Solaris 8 system I get: Skipping test: no transitional chinese locale is installed SKIP: test-mbrtowc4.sh Therefore can yo

Re: upstream regex

[CCing bug-gnulib. This is a reply to ] Hello Tony, > > Suggestion: Use the same logic for restrict and restrict_arr as in > > gnulib/lib/regex.h. > > What is considered the authoritative source of regex.h? Is it the glibc > sou

Re: c-strtod: handling of out-of-memory

Bruno Haible wrote: > Yup, thanks. Committed with this fix, and a bit nicer formatting: Nicer indeed. > +/* Parse the initial portion of the string pointed to by NPTR as a floating- > + point number (in decimal or hexadecimal notation), like in the C locale: > + accepting only the ASCII digi

Re: c-strtod: handling of out-of-memory

Hi Jim, > Thanks for writing that. One nit: s/the a/a/ Yup, thanks. Committed with this fix, and a bit nicer formatting: 2009-01-24 Bruno Haible * lib/c-strtod.h (c_strtod, c_strtold): Add specification. --- lib/c-strtod.h.orig 2009-01-24 11:42:56.0 +0100 +++ lib/c-strtod.

Re: c-strtod: handling of out-of-memory

Bruno Haible wrote: > 2009-01-23 Bruno Haible > > * lib/c-strtod.h (c_strtod, c_strtold): Add specification. Hi Bruno, > --- lib/c-strtod.h.orig 2009-01-24 00:08:16.0 +0100 > +++ lib/c-strtod.h2009-01-24 00:07:51.0 +0100 ... > + If successful, return the valu