public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Keisuke Nishida <kxn30@po.cwru.edu>
To: guile-emacs@sourceware.cygnus.com
Subject: Re: pass by value / pass by reference
Date: Wed, 15 Mar 2000 16:37:00 -0000	[thread overview]
Message-ID: <m3n1nz7nrw.fsf@kei.cwru.edu> (raw)
In-Reply-To: <m3pusv7o8i.fsf@kei.cwru.edu>

Keisuke Nishida <kxn30@po.cwru.edu> writes:

> One problem of my current implementation is that whenever one
> interpreter calls the other one, the arguments are converted
> into the other type; that is, they are passed by value.  This
> works fine for some cases, but sometimes it is necessary to pass
> them by reference.

Not exactly.  I mean:

 [ Value Model ]

           scheme-eval            lisp-eval
  Lisp obj ----------> Scheme obj --------> Lisp obj


 [ Reference Model ]

           scheme-eval            lisp-eval
  Lisp obj ----------> Lisp ptr   --------> Lisp obj
                    (as Scheme obj)

So, we are going to import all Lisp objects as pointers.

      reply	other threads:[~2000-03-15 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-15 16:27 Keisuke Nishida
2000-03-15 16:37 ` Keisuke Nishida [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3n1nz7nrw.fsf@kei.cwru.edu \
    --to=kxn30@po.cwru.edu \
    --cc=guile-emacs@sourceware.cygnus.com \
    /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).