string-every returns #f when applied to an empty sequence

2004-07-30 Thread Andreas Vögele
According to SRFI-13 the procedure string-every returns #t if it is applied to an empty sequence (see http://srfi.schemers.org/srfi-13/srfi-13.html#Predicates). But Guile's implementation returns #f. Is this a bug in SRFI-13 or in srfi/srfi-13.c? ___

[patch] 1.6.4: configure syntax error with autoconf 2.59

2004-07-30 Thread Maciej W. Rozycki
Hello, As of autoconf 2.59 due to the way AC_LIBOBJ gets expanded, the resulting configure script contains ; fi alone in a line, which is not accepted at least by bash 2.05b. Here is an obvious fix. 2004-07-30 Maciej W. Rozycki [EMAIL PROTECTED] * configure.in: Reformat a

[patch] 1.6.4: aclocal 1.8 compatibility

2004-07-30 Thread Maciej W. Rozycki
Hello, Since automake 1.8 aclocal requires macro names being defined by AC_DEFUN to be quoted. Here is a patch that adds missing quotations. 2004-07-30 Maciej W. Rozycki [EMAIL PROTECTED] * acinclude.m4: Quote names of macros to be defined by AC_DEFUN throughout. *

Re: string-every returns #f when applied to an empty sequence

2004-07-30 Thread Kevin Ryde
Andreas Vögele [EMAIL PROTECTED] writes: According to SRFI-13 the procedure string-every returns #t if it is applied to an empty sequence (see http://srfi.schemers.org/srfi-13/srfi-13.html#Predicates). But Guile's implementation returns #f. Is this a bug in SRFI-13 or in srfi/srfi-13.c?

Re: [patch] 1.6.4: configure syntax error with autoconf 2.59

2004-07-30 Thread Kevin Ryde
Maciej W. Rozycki [EMAIL PROTECTED] writes: As of autoconf 2.59 due to the way AC_LIBOBJ gets expanded, the resulting configure script contains ; fi alone in a line, which is not accepted at least by bash 2.05b. Thanks, that's been fixed in the cvs I think.

Re: [patch] 1.6.4: aclocal 1.8 compatibility

2004-07-30 Thread Kevin Ryde
Maciej W. Rozycki [EMAIL PROTECTED] writes: Since automake 1.8 aclocal requires macro names being defined by AC_DEFUN to be quoted. Here is a patch that adds missing quotations. Thanks, I made that change. (Not sure what automake version will actually be used for the next release though.)