unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Daniel Kraft <d@domob.eu>
Cc: guile-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: GSoC: Emacs  Lisp support for GNU Guile
Date: Tue, 31 Mar 2009 16:05:42 -0700	[thread overview]
Message-ID: <m3zlf1mgxl.fsf@pobox.com> (raw)
In-Reply-To: <gqtrhe$80m$1@ger.gmane.org> (Daniel Kraft's message of "Tue, 31 Mar 2009 21:44:11 +0200")

Hi Daniel,

On Tue 31 Mar 2009 12:44, Daniel Kraft <d@domob.eu> writes:

> as already discussed briefly with the Guile guys behind the new VM
> thing, I got the idea to implement Emacs Lisp as supported language for
> the Guile VM system.

This sounds great! I'd love to assist. As the fellow who's hacked most
on Guile's VM, I can offer "mentorship" if you like, on the Guile
side -- though I am not as knowledgable about Emacs as I'd like to be.

I'll direct replies to further Guile-type details to the Guile list, but
in summary:

> Originally, Guile as the GNU scripting language was designed as a language
> based on the Scheme lisp dialect; however, as a prime example for use of a
> scripting language (and with a huge existing base of scripts) Emacs Lisp is
> another popular lisp based scripting language.  With the new capabilities of
> Guile, it will be possible to add support of this language to Guile and thus
> allow it (and all programs using Guile as scripting engine) to be
> programmed not
> only in Scheme but also Emacs lisp; thus, it will also be possible to
> utilize
> all the existing elisp code for creating even more nifty and useful
> scripts.

YMMV, but I think that elisp is most useful within the context of Emacs
itself -- its data types, its libraries, its runtime. So after getting
Emacs Lisp's semantics to compile, perhaps as a "if time allows" thing,
defining a Guile implementation of emacs/src/lisp.h would allow Guile to
slip into Emacs with minimal modification of C sources.

Or perhaps it's better to limit this SOC to just the Scheme side of
things? Dunno.

In any case, I think with "world enough and time", Guile can do whatever
it takes to provide a faster, better Elisp implementation -- including
adding Elisp-specific ops to its VM, if necessary.

> Communication:
>
> Depends on the requests from my mentor / the community, but I think the
> public development mailing lists and private email should be fine; other
> ideas
> are instant messaging / IRC.

I'm often on #guile, with CET as my timezone. Between there and the
mailing lists we should be good, avoiding private email.

I hope this works out!

Andy
-- 
http://wingolog.org/




  parent reply	other threads:[~2009-03-31 23:05 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
2009-03-31 23:05 ` Andy Wingo [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=m3zlf1mgxl.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=d@domob.eu \
    --cc=emacs-devel@gnu.org \
    --cc=guile-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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