unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Brian Templeton <bpt@tunes.org>
To: guile-devel@gnu.org
Cc: wingo@pobox.com, raeburn@mit.edu
Subject: guile-emacs for gsoc
Date: Wed, 07 Apr 2010 15:55:28 -0400	[thread overview]
Message-ID: <878w8z9gwf.fsf@lupus.terpri.org> (raw)

Hello Guile hackers,

I'm preparing Summer of Code applications and am considering working on
Emacs-Guile integration. Here's my understanding of the current
situation, from skimming list archives, source code, etc.:

* Guile now has a partial implementation of Emacs Lisp, and it mostly
  works although a few features are missing

* Ken Raeburn has done proof-of-concept work to make Emacs use Guile's
  object representation and GC for Emacs Lisp, which is now outdated but
  shows that it's feasible (and perhaps it could be forward-ported?)

* Emacs Lisp interaction is pervasive throughout much of the Emacs C
  code, but I don't know how well-abstracted it is

* Once Guile's Emacs Lisp support is sufficiently good, Guile can be
  swapped in for the Emacs Lisp evaluator

I'm not yet familiar with the relevant bits of Guile and Emacs internals
(though I've worked on other Lisp implementations), and I only started
following Guile development recently. So my question is, where could I
best focus my efforts for two months of full-time work (plus a month of
relatively free time before GSoC officially begins)? One obvious project
would be to finish up the Emacs Lisp implementation; I just started
looking at it last night, so I don't know how complete it really is.
Another might be to go ahead with replacing the Emacs Lisp evaluator
even if Guile's Emacs Lisp implementation is not quite complete, enough
to get it booting (and then improving the Emacs Lisp language
implementation would have immediate benefits). And then there are side
projects like writing a bytecode interpreter.

If you have feedback for my application, you'll have to respond before
19:00 UTC on Friday. (My apologies for the late message! I was working
on a rather different proposal, and only found out recently that there
is significant active interest in Guile-Emacs.) Of course I'm still
interested in discussing it after then, and any suggestions are helpful.

thanks,
bpt
-- 
Inteligenta persono lernas la lingvon Esperanton rapide kaj facile.
Esperanto estas moderna, kultura lingvo por la mondo. Simpla, fleksebla,
belsona, Esperanto estas la praktika solvo de la problemo de universala
interkompreno. Lernu la interlingvon Esperanton! http://lernu.net/




             reply	other threads:[~2010-04-07 19:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 19:55 Brian Templeton [this message]
2010-04-07 20:58 ` guile-emacs for gsoc Andy Wingo
2010-04-07 21:18   ` Ludovic Courtès
2010-04-08  3:39 ` Ken Raeburn
  -- strict thread matches above, loose matches on Subject: below --
2010-04-07 20:05 Brian Templeton
2010-04-07 20:55 ` Daniel Kraft

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=878w8z9gwf.fsf@lupus.terpri.org \
    --to=bpt@tunes.org \
    --cc=guile-devel@gnu.org \
    --cc=raeburn@mit.edu \
    --cc=wingo@pobox.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).