Re: getaddrinfo.c: don't require snprintf; new function: shorttostr

2006-10-23 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> > +# Prerequisites of lib/uinttostr.c. >> > +AC_DEFUN([gl_PREREQ_UINTTOSTR], [:]) >> >> What are these dummy functions useful for, anyway? > > They separate the autoconf macros needed to determine _when_ to enable a > replacemen

Re: an introduction to gnulib

2006-10-23 Thread Karl Berry
I hope this fulfills the need of an introduction to gnulib. This is great. Thanks Bruno. I fixed a few Texinfo niglets. Best, Karl

Re: getaddrinfo.c: don't require snprintf; new function: shorttostr

2006-10-23 Thread Jim Meyering
Eric Blake-1 <[EMAIL PROTECTED]> wrote: > I checked this in: > > 2006-10-23 Eric Blake <[EMAIL PROTECTED]> > > * lib/getaddrinfo.c (includes): Add missing include. Thanks!

Re: getaddrinfo.c: don't require snprintf; new function: shorttostr

2006-10-23 Thread Eric Blake-1
> I've checked it in: > > 2006-10-23 Jim Meyering <[EMAIL PROTECTED]> > > * lib/getaddrinfo.c (getnameinfo): Use new lightweight uinttostr, > in place of snprintf. You missed a piece: gcc -Wall -DHAVE_CONFIG_H -I. -I.. -I../../gllib -g -O2 -MT getaddrinfo.o -MD -MP -MF .deps/

Re: renaming obstack_free

2006-10-23 Thread Bruno Haible
Paul Eggert wrote: > if we uniformly substitute __obstack_free for _obstack_free, and omit the > change's last hunk, then the change should be OK for glibc. Thanks for the advice. I committed this. 2006-10-23 Bruno Haible <[EMAIL PROTECTED]> Paul Eggert <[EMAIL PROTECTED]>

Re: renaming obstack_free

2006-10-23 Thread Paul Eggert
Bruno Haible <[EMAIL PROTECTED]> writes: > I propose this one. Paul, do you think you can push that into glibc? I think glibc would take that change, yes. I'll put it on my list of things to do. > * lib/obstack.h (_obstack_free): New macro. Declare instead of > obstack_free. That d

Re: getaddrinfo.c: don't require snprintf; new function: shorttostr

2006-10-23 Thread Paul Eggert
>> What are these dummy functions useful for, anyway? > > They're just place-holders. They are place-holders so often that I've come to omit them if I think they'll always be place-holders. I think it's a matter of style as much as anything.

Re: [bug-gnulib] gnulib-tool: fix for platforms with bash 2.x

2006-10-23 Thread Bruno Haible
Daniel Jacobowitz wrote: > > ! echo " @MOSTLYCLEANDIRS=\"\$(MOSTLYCLEANDIRS)\" \\" I think a semicolon is missing after the assignment. > > ! echo " test -z \"\$\$MOSTLYCLEANDIRS\" || \\" This is not needed usually (except if you care about very old shells). > > ! echo "for dir in \

Re: [bug-gnulib] Re: getaddrinfo.c: don't require snprintf; new function: shorttostr

2006-10-23 Thread Bruno Haible
Simon Josefsson wrote: > > +# Prerequisites of lib/uinttostr.c. > > +AC_DEFUN([gl_PREREQ_UINTTOSTR], [:]) > > What are these dummy functions useful for, anyway? They separate the autoconf macros needed to determine _when_ to enable a replacement from the autoconf macros needed for compiling the r

Re: getaddrinfo.c: don't require snprintf; new function: shorttostr

2006-10-23 Thread Jim Meyering
Simon Josefsson <[EMAIL PROTECTED]> wrote: > ... >> +# Prerequisites of lib/uinttostr.c. >> +AC_DEFUN([gl_PREREQ_UINTTOSTR], [:]) > > What are these dummy functions useful for, anyway? Not much. They're just place-holders.

Re: gnulib-tool: fix for platforms with bash 2.x

2006-10-23 Thread Daniel Jacobowitz
On Mon, Oct 23, 2006 at 02:15:58PM +0200, Bruno Haible wrote: > Hi, > > All versions of bash grok >for f in $VAR; do ...; done > where VAR is an empty shell variable. But >for f in $(VAR); do ...; done > where $(VAR) is an empty Makefile variable, leads to a syntax error with > bash 2.00..

Re: getaddrinfo.c: don't require snprintf; new function: shorttostr

2006-10-23 Thread Simon Josefsson
Jim Meyering <[EMAIL PROTECTED]> writes: > If you prefer uint16_t over "unsigned short int" we can try that, but > since that type is used solely for a temporary, with no risk of sign > extension its width shouldn't matter, and with the latter, we don't > have to worry about whether the type is de

new module 'tsearch'

2006-10-23 Thread Bruno Haible
Hi, mingw has but it lacks the tsearch family of functions for managing binary trees. Here's a proposal to add a substitute, taken from glibc. For simplicity, I don't add a substitute for all of (queues, hash tables, linear search, tree search), but instead introduce a header tsearch.h (like we

an introduction to gnulib

2006-10-23 Thread Bruno Haible
Hi, I hope this fulfills the need of an introduction to gnulib. 2006-10-22 Bruno Haible <[EMAIL PROTECTED]> * doc/gnulib-intro.texi: New file. * doc/gnulib.texi: Include it. diff -r -c3 --new-file --exclude=CVS gnulib-20061020/doc/gnulib-intro.texi gnulib-20061020-modified/do

gnulib documentation structure

2006-10-23 Thread Bruno Haible
Hi, I'm restructuring the gnulib documentation: 1) to separate the random notes from the documentation of individual modules, 2) to move the gnulib-tool invocation before all these detail descriptions, because how to use gnulib-tool is now important for every gnulib user. 2006-10-21 Bru

gnulib-tool: fix for platforms with bash 2.x

2006-10-23 Thread Bruno Haible
Hi, All versions of bash grok for f in $VAR; do ...; done where VAR is an empty shell variable. But for f in $(VAR); do ...; done where $(VAR) is an empty Makefile variable, leads to a syntax error with bash 2.00..2.05. The solution is ugly... 2006-10-21 Bruno Haible <[EMAIL PROTECTED]>

renaming obstack_free

2006-10-23 Thread Bruno Haible
Hi, To follow the Ralf's advice for gnulib code in shared libraries, one needs to rename the exported symbols. Among those, one finds 'obstack_free' from the obstack module. Renaming this one is not easy, because 1. it occurs in obstack.h both as macro and as function name, 2. any patch should

Re: [bug-gnulib] argp and MinGW

2006-10-23 Thread Bruno Haible
Paul Eggert wrote: > Bruno Haible <[EMAIL PROTECTED]> writes: > > > * lib/argp.h (argp_parse, __argp_parse): Use _argc, _argv as argument > > names, not __argc, __argv. (The latter are defined as macros on mingw.) > > glibc headers must also be robust against user code that does "#define