From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Daniel Kraft <d@domob.eu>, guile-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: GSoC: Emacs Lisp support for GNU Guile
Date: Tue, 31 Mar 2009 16:15:26 -0700 [thread overview]
Message-ID: <m3r60dmghd.fsf@pobox.com> (raw)
In-Reply-To: <87vdppnxfo.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Tue, 31 Mar 2009 23:23:55 +0100")
Hi Neil :)
Though I was not the person to whom the question was addressed, a
comment :)
On Tue 31 Mar 2009 15:23, Neil Jerram <neil@ossau.uklinux.net> writes:
> If you followed this kind of approach, note that it would also need
> work - in addition to the Elisp/VM translation - to implement whatever
> Emacs primitives the Elisp code relies on. That would make the
> project as a whole less pure-language-translation, but (in my view)
> more real and useful.
I keep thinking that it should be possible to write some kind of C shim
so that Guile could implement the Emacs C "API". That way we keep the
existing C code working, we keep the fine-tuned implementations and
semantics, and we can move on from "re-implementing" to "implementing"
-- e.g. adding to Emacs instead of just reproducing it.
Happy hacking,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-03-31 23:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 19:44 GSoC: Emacs Lisp support for GNU Guile Daniel Kraft
2009-03-31 20:28 ` Clinton Ebadi
2009-04-04 22:00 ` Richard M Stallman
2009-03-31 22:23 ` Neil Jerram
2009-03-31 23:15 ` Andy Wingo [this message]
2009-03-31 23:05 ` Andy Wingo
2009-03-31 23:41 ` Neil Jerram
2009-04-01 15:36 ` Daniel Kraft
2009-04-01 13:31 ` Stefan Monnier
2009-04-03 17:30 ` Andy Wingo
2009-04-03 20:31 ` Chong Yidong
2009-04-03 23:50 ` Andy Wingo
2009-04-06 23:26 ` Samuel Bronson
2009-04-07 0:52 ` Stefan Monnier
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=m3r60dmghd.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=d@domob.eu \
--cc=emacs-devel@gnu.org \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.