From: Jim Blandy <jimb@red-bean.com>
To: Keisuke Nishida <kxn30@po.cwru.edu>
Cc: Kalle Olavi Niemitalo <tosi@ees2.oulu.fi>,
guile-emacs@sourceware.cygnus.com
Subject: Re: guile-emacs GC (was special forms)
Date: Wed, 15 Mar 2000 13:48:00 -0000 [thread overview]
Message-ID: <m34sa79a6q.fsf@savonarola.red-bean.com> (raw)
In-Reply-To: <m37lf47zrg.fsf@kei.cwru.edu>
> Seriously, I think we have to make some restrictions on Lisp
> programs so they don't keep Scheme values. I think people of
> Guile Emacs do not want to write new programs in Lisp, so it's
> not a problem. If people of Lisp want to use Guile's features,
> it is the time to move to the Guile-based Emacs.
Honestly, this doesn't seem like a good idea. There are zillions of
useful Emacs Lisp functions that are part of Emacs right now, and it
would be a fatal mistake to push a design which doesn't encourage the
Lisp and Scheme worlds to share data freely.
The best approach is to change Emacs Lisp to use Guile objects. That
is, Fcons (if I remember correctly) should call SCM_NEWCELL, and so
on. That way, the two languages operate on a common GC, and can share
data freely.
Ken Raeburn has already done a lot of this work. You really should
look at his patches.
next prev parent reply other threads:[~2000-03-15 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-14 12:46 special forms (save-excursion) Kalle Olavi Niemitalo
2000-03-14 13:32 ` Keisuke Nishida
2000-03-14 14:11 ` Keisuke Nishida
2000-03-14 14:17 ` Keisuke Nishida
2000-03-15 0:34 ` Kalle Olavi Niemitalo
2000-03-15 3:32 ` Keisuke Nishida
2000-03-15 5:11 ` Kalle Olavi Niemitalo
2000-03-15 5:43 ` Keisuke Nishida
2000-03-15 6:12 ` Kalle Olavi Niemitalo
2000-03-15 11:37 ` guile-emacs GC (was special forms) Kalle Olavi Niemitalo
2000-03-15 12:18 ` Keisuke Nishida
2000-03-15 13:48 ` Jim Blandy [this message]
2000-03-15 15:14 ` Keisuke Nishida
2000-03-15 11:30 ` special forms (save-excursion) Kalle Olavi Niemitalo
2000-03-15 12:42 ` Keisuke Nishida
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=m34sa79a6q.fsf@savonarola.red-bean.com \
--to=jimb@red-bean.com \
--cc=guile-emacs@sourceware.cygnus.com \
--cc=kxn30@po.cwru.edu \
--cc=tosi@ees2.oulu.fi \
/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).