unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: <dsmich@roadrunner.com>
Cc: guile-user@gnu.org, David Kastrup <dak@gnu.org>
Subject: Re: Multiple values passed as single argument to procedure
Date: Mon, 26 Jun 2017 19:25:04 +0800	[thread overview]
Message-ID: <87injj9ejz.fsf@gmail.com> (raw)
In-Reply-To: <20170613111720.XPOJR.173377.root@cdptpa-web11> (dsmich@roadrunner.com's message of "Tue, 13 Jun 2017 7:17:19 -0400")

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

Here is an explanation of multiple values by Oleg[0] and an
implementation from the Scheme book[1]. These are more advanced
stuff. Honestly, I usually don't understand what Oleg said. But it is
good to know these references. It is like math, one day when you have
enough background and the right perspective, you will understand what's
going on.

[0]: http://okmij.org/ftp/Scheme/misc.html#multiple-value-effect
[1]: http://www.scheme.com/tspl4/control.html#./control:h8

<dsmich@roadrunner.com> writes:

> ---- 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-06-26 11:25 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
2017-06-26 11:25                   ` Alex Vong [this message]
  -- 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=87injj9ejz.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --cc=dak@gnu.org \
    --cc=dsmich@roadrunner.com \
    --cc=guile-user@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).