* string-every returns #f when applied to an empty sequence
@ 2004-07-30 8:16 "Andreas Vögele"
2004-07-31 1:49 ` Kevin Ryde
0 siblings, 1 reply; 4+ messages in thread
From: "Andreas Vögele" @ 2004-07-30 8:16 UTC (permalink / raw)
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?
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: string-every returns #f when applied to an empty sequence
2004-07-30 8:16 string-every returns #f when applied to an empty sequence "Andreas Vögele"
@ 2004-07-31 1:49 ` Kevin Ryde
2004-08-13 6:39 ` Rob Browning
0 siblings, 1 reply; 4+ messages in thread
From: Kevin Ryde @ 2004-07-31 1:49 UTC (permalink / raw)
Cc: bug-guile
"Andreas Vögele" <voegelas@gmx.net> 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?
Thanks. If it's contrary to the spec then it's a bug in guile.
Looks like guile also doesn't make the final predicate application a
tail call the way the spec describes. Not sure how to fix that.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: string-every returns #f when applied to an empty sequence
2004-07-31 1:49 ` Kevin Ryde
@ 2004-08-13 6:39 ` Rob Browning
2004-08-14 0:34 ` Kevin Ryde
0 siblings, 1 reply; 4+ messages in thread
From: Rob Browning @ 2004-08-13 6:39 UTC (permalink / raw)
Cc: bug-guile
Kevin Ryde <user42@zip.com.au> writes:
> Thanks. If it's contrary to the spec then it's a bug in guile.
>
> Looks like guile also doesn't make the final predicate application a
> tail call the way the spec describes. Not sure how to fix that.
Actually, we can change it so that we handle the last invocation
specially, i.e. "return scm_call_1(...);".
If we're going to implement string-every in C, then that's the best we
can do right now, and from looking at the output of srfi-13.s via
-save-temps (presuming I'm reading the x86 assembly right) newer gcc's
optimize that call to a jmp.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: string-every returns #f when applied to an empty sequence
2004-08-13 6:39 ` Rob Browning
@ 2004-08-14 0:34 ` Kevin Ryde
0 siblings, 0 replies; 4+ messages in thread
From: Kevin Ryde @ 2004-08-14 0:34 UTC (permalink / raw)
Cc: bug-guile
Rob Browning <rlb@defaultvalue.org> writes:
>
> If we're going to implement string-every in C, then that's the best we
> can do right now, and from looking at the output of srfi-13.s via
> -save-temps (presuming I'm reading the x86 assembly right) newer gcc's
> optimize that call to a jmp.
I wouldn't worry, unless everything else in the eval path is optimized
that way too. Even then it's relying on a new enough gcc.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-08-14 0:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-30 8:16 string-every returns #f when applied to an empty sequence "Andreas Vögele"
2004-07-31 1:49 ` Kevin Ryde
2004-08-13 6:39 ` Rob Browning
2004-08-14 0:34 ` Kevin Ryde
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).