From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: djurfeldt@nada.kth.se
Subject: Re: parallel with no exprs
Date: Mon, 16 Jun 2003 20:45:19 +0200 [thread overview]
Message-ID: <xy71xxt6ev4.fsf@nada.kth.se> (raw)
In-Reply-To: <87y9057d4y.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 14 Jun 2003 09:48:13 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> 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.
No. In fact, I'm not sure at all. In fact,
I am no longer the Guile developer who says "(parallel) should expand
to (begin)". I am now the Guile developer who says "(parallel) should
expand to (values)"!
Please do apply your patch.
(Sorry for not paying attention.)
> (I'm not especially worried one way or the other, I only arrived at it
> from looking to add to the manual.)
Good thing to express things with words...
>> 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 :-).
The question is if (begin) --> #<unspecified> is correct. Probably
so, because (begin) is a sequence and it should probably always return
1 value...
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-06-16 18:45 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
2003-06-16 18:45 ` Mikael Djurfeldt [this message]
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=xy71xxt6ev4.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
/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).