From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: guile-devel@gnu.org
Subject: Re: for-each and varargs
Date: Mon, 10 Feb 2003 13:43:23 +0100 [thread overview]
Message-ID: <xy7adh4l310.fsf@nada.kth.se> (raw)
In-Reply-To: <87of5lf5r5.fsf@zip.com.au> (Kevin Ryde's message of "Mon, 10 Feb 2003 08:28:46 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> In the latest cvs built on a recent i386 debian, for-each doesn't
> always seem to like a procedure taking a variable number of arguments.
> For instance foo.scm,
>
> (for-each (lambda (x . y) (display x))
> '(1 2 3))
>
> run with "guile -s foo.scm" gives
>
> ERROR: In procedure for-each:
> ERROR: Wrong type argument in position 1: #<procedure #f (x . y)>
>
> whereas I hoped it would display `123'.
* eval.c (scm_trampoline_0, scm_trampoline_1, scm_trampoline_2):
Fixed formals tests for closures. (Thanks to Kevin Ryde.)
Silly me. I've been a bit careless when implementing this one.
> Curiously this is what it does when run interatively, not with
> "guile -s".
That's because "guile -s" uses the "normal" evaluator by default.
for-each doesn't use an optimized strategy when the debugging
evaluator is active. This is to get a more informative backtrace.
Best regards,
Mikael D.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-02-10 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 22:28 for-each and varargs Kevin Ryde
2003-02-10 12:43 ` Mikael Djurfeldt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xy7adh4l310.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).