Re: choice of implementation language

2009-01-07 Thread Simon Josefsson
Ralf Wildenhues ralf.wildenh...@gmx.de writes: Hello, Jim Meyering j...@meyering.net writes: So I conclude that the choices are Perl Python Ruby FWIW, my preferences are: sticking with what we currently have, or Perl. Yeah, I forgot to say that: I don't see a critical

Re: choice of implementation language

2009-01-07 Thread Mike Frysinger
On Wednesday 07 January 2009 09:39:06 Sam Steingold wrote: Bruno Haible wrote: If gnulib-tool was to be rewritten in another programming language than shell + sed, what would be the good choices? a popularity contest is not the way to choose a language. and why aren't you even considering

Re: choice of implementation language

2009-01-07 Thread Jose E. Marchesi
On Wednesday 07 January 2009 09:39:06 Sam Steingold wrote: Bruno Haible wrote: If gnulib-tool was to be rewritten in another programming language than shell + sed, what would be the good choices? a popularity contest is not the way to choose a language. and why aren't you even

Re: choice of implementation language

2009-01-07 Thread Sam Steingold
Mike Frysinger wrote: On Wednesday 07 January 2009 09:39:06 Sam Steingold wrote: Bruno Haible wrote: If gnulib-tool was to be rewritten in another programming language than shell + sed, what would be the good choices? a popularity contest is not the way to choose a language. and why aren't

Re: choice of implementation language

2009-01-07 Thread Mike Frysinger
On Wednesday 07 January 2009 11:12:57 Sam Steingold wrote: Mike Frysinger wrote: On Wednesday 07 January 2009 09:39:06 Sam Steingold wrote: Bruno Haible wrote: If gnulib-tool was to be rewritten in another programming language than shell + sed, what would be the good choices? a

Re: PATCH: Fix poll() impl on Win32

2009-01-07 Thread Jim Meyering
Daniel P. Berrange berra...@redhat.com wrote: I've been using the GNULIB poll() impl in libvirt on Win32 (well Mingw + WINE) and found it was producing really wierd results, such ret=-1 + errno=EAGAIN, or ret=0 even though requested timeout was infinite. After a little debugging I discovered a

Re: PATCH: Fix poll() impl on Win32

2009-01-07 Thread Paolo Bonzini
Jim Meyering wrote: Daniel P. Berrange berra...@redhat.com wrote: I've been using the GNULIB poll() impl in libvirt on Win32 (well Mingw + WINE) and found it was producing really wierd results, such ret=-1 + errno=EAGAIN, or ret=0 even though requested timeout was infinite. After a little

Re: PATCH: Fix poll() impl on Win32

2009-01-07 Thread Jim Meyering
Jim Meyering j...@meyering.net wrote: Daniel P. Berrange berra...@redhat.com wrote: I've been using the GNULIB poll() impl in libvirt on Win32 (well Mingw + WINE) and found it was producing really wierd results, such ret=-1 + errno=EAGAIN, or ret=0 even though requested timeout was infinite.

PATCH: Fix poll() impl on Win32

2009-01-07 Thread Daniel P. Berrange
I've been using the GNULIB poll() impl in libvirt on Win32 (well Mingw + WINE) and found it was producing really wierd results, such ret=-1 + errno=EAGAIN, or ret=0 even though requested timeout was infinite. After a little debugging I discovered a missing initialization of the 'rc' variable in