From: Kevin Ryde <user42@zip.com.au>
Subject: Re: parallel with no exprs
Date: Sat, 14 Jun 2003 09:48:13 +1000 [thread overview]
Message-ID: <87y9057d4y.fsf@zip.com.au> (raw)
In-Reply-To: <xy7of13y7al.fsf@nada.kth.se> (Mikael Djurfeldt's message of "Thu, 12 Jun 2003 11:27:46 +0200")
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
>
> Oops. The second lambda should have (x) as formal parameters.
> But this error is independent from the problem we are discussing.
> (parallel) correctly expands to (begin).
Are you sure you want it that way? I guess it'd be necessary to
document that parallel of N forms returns N values except that 0 forms
returns 1 unspecified value.
Maybe 0 forms shouldn't be documented at all, could quietly ignore it
as too degenerate.
(I'm not especially worried one way or the other, I only arrived at it
from looking to add to the manual.)
> In our implementation,
> (begin) evaluates to #<unspecified> which is 1 value, so the second
> lambda must take 1 argument.
Yes I thought it might be the unspecified literalism, or rather the
literalism of unspecified :-).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-06-13 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 22:07 parallel with no exprs Kevin Ryde
2003-06-09 8:35 ` Mikael Djurfeldt
2003-06-12 1:54 ` Kevin Ryde
2003-06-12 9:27 ` Mikael Djurfeldt
2003-06-13 23:48 ` Kevin Ryde [this message]
2003-06-16 18:45 ` Mikael Djurfeldt
2003-06-19 1:40 ` Kevin Ryde
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=87y9057d4y.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).