Re: working with "good enough" functions

2009-01-08 Thread Mike Frysinger
On Thursday 08 January 2009 11:55:03 Simon Josefsson wrote: > Mike Frysinger writes: > > On Thursday 08 January 2009 04:49:16 Paul Eggert wrote: > >> Mike Frysinger writes: > >> > i explicitly pulled in the > >> > printf-posix module because i want a posix implementation on crappy > >> > systems.

Re: working with "good enough" functions

2009-01-08 Thread Simon Josefsson
Mike Frysinger writes: > On Thursday 08 January 2009 04:49:16 Paul Eggert wrote: >> Mike Frysinger writes: >> > i explicitly pulled in the >> > printf-posix module because i want a posix implementation on crappy >> > systems. but i dont care if said systems have broken floating point >> > implem

Re: working with "good enough" functions

2009-01-08 Thread Mike Frysinger
On Thursday 08 January 2009 04:49:16 Paul Eggert wrote: > Mike Frysinger writes: > > i explicitly pulled in the > > printf-posix module because i want a posix implementation on crappy > > systems. but i dont care if said systems have broken floating point > > implementations since i dont use float

Re: working with "good enough" functions

2009-01-08 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paul Eggert on 1/8/2009 2:49 AM: > If this happens often enough, perhaps gnulib should have a > printf-posix-no-fp module that does what you want? The newlib library, and thus cygwin, go so far as to provide the *iprintf family of functio

Re: choice of implementation language

2009-01-08 Thread James Youngman
Please note that my contributions to gnulib-tool so far have been nonexistent; weigh my statements accordingly... On Sun, Jan 4, 2009 at 10:25 PM, Bruno Haible wrote: > If gnulib-tool was to be rewritten in another programming language than > shell + sed, what would be the good choices? > > The f

Re: working with "good enough" functions

2009-01-08 Thread Paul Eggert
Mike Frysinger writes: > i explicitly pulled in the > printf-posix module because i want a posix implementation on crappy systems. > but i dont care if said systems have broken floating point implementations > since i dont use floating point in my code. If this happens often enough, perhaps