From: <dsmich@roadrunner.com>
To: David Kastrup <dak@gnu.org>, Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org
Subject: Re: Multiple values passed as single argument to procedure
Date: Tue, 13 Jun 2017 7:17:19 -0400 [thread overview]
Message-ID: <20170613111720.XPOJR.173377.root@cdptpa-web11> (raw)
In-Reply-To: <87h8zk1v3v.fsf@netris.org>
---- Mark H Weaver <mhw@netris.org> wrote:
> David Kastrup <dak@gnu.org> writes:
>
> > Mark H Weaver <mhw@netris.org> writes:
> >ument
> >> I'm sorry David, but _everything_ that you wrote below is incorrect.
> >
> > Well, let me try again. It's not all that easy to understand.
>
> You're obviously quite intelligent and knowledgeable, so it's probably
> my failure to explain it well more than anything else. We can try again
> together.
Thanks Mark for that most excellently lucid explanation! I had vague notions before
but I have a much deeper appreciation now.
Back in the day, I used Forth a bit. Multiple arguments and multiple return values
were pretty much the same thing. (the stack) And it was easy, because of the syntax
of the language. Yeah, I agree, syntax is the main blocker here.
Thanks again!
-Dale
next prev parent reply other threads:[~2017-06-13 11:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 7:56 Multiple values passed as single argument to procedure Chris Marusich
2017-06-11 8:28 ` David Kastrup
2017-06-11 20:36 ` Mark H Weaver
2017-06-11 21:31 ` Mark H Weaver
2017-06-12 0:19 ` Chris Marusich
2017-06-12 4:25 ` Mark H Weaver
2017-06-12 8:19 ` Chris Marusich
2017-06-12 8:55 ` Neil Jerram
2017-06-12 9:48 ` Neil Jerram
2017-06-12 9:39 ` David Kastrup
2017-06-12 11:31 ` Mark H Weaver
2017-06-12 14:24 ` David Kastrup
2017-06-13 2:26 ` Mark H Weaver
2017-06-13 3:09 ` Mark H Weaver
2017-06-13 3:45 ` Mark H Weaver
2017-06-13 11:17 ` dsmich [this message]
2017-06-26 11:25 ` Alex Vong
-- strict thread matches above, loose matches on Subject: below --
2017-09-01 19:39 Chris Marusich
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=20170613111720.XPOJR.173377.root@cdptpa-web11 \
--to=dsmich@roadrunner.com \
--cc=dak@gnu.org \
--cc=guile-user@gnu.org \
--cc=mhw@netris.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).