unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: BT Templeton <bpt@hcoop.net>
To: guile-devel@gnu.org
Subject: Re: gnu in summer-of-code: more projects needed
Date: Wed, 06 Apr 2011 17:22:18 -0400	[thread overview]
Message-ID: <87fwpv6po5.fsf@olor.terpri.org> (raw)
In-Reply-To: 877hb9g1d9.fsf@gnu.org

ludo@gnu.org (Ludovic Courtès) writes:

> Saluton Brian,
>
> BT Templeton <bpt@hcoop.net> writes:
>
>> I'd like to continue my work on the Emacs Lisp compiler.
>
> Would be great!
>
>> Some areas that could use improvement:
>>
>>  * Implement Emacs-compatible lexical binding support
>
> In what way is the current elisp implementation in Guile not
> Emacs-compatible?

This is a trivial change; Emacs uses the `lexical-binding' variable to
determine the default scope rules on a per-file basis, while Guile-Elisp
provides a `lexical-let' special form.

>>  * Many Elisp subrs are not implemented in Guile-Elisp; some don't make
>>    sense outside of Emacs, but the rest should be provided. I wrote
>>    simple versions of many subrs in Elisp (using guile-ref, etc.), but
>>    only just enough for subr.el to load more or less correctly.
>>
>>  * A more comprehensive testing framework would be nice. For example,
>>    I'd like to be able to run Elisp tests in both Guile and Emacs.
>>
>>  * "Big variables," as proposed in
>>    <http://article.gmane.org/gmane.lisp.guile.devel/10750>, would
>>    simplify the implementation, and would also be useful if anyone wants
>>    to implement support for other Lisp-2 dialects in the future.
>>
>>  * Nil needs to be a list, a boolean, *and* a symbol, not just a list
>>    and a boolean.
>>
>>  * Guile-Elisp needs to support aliases and buffer-local variables.
>>
>>  * Guile-Elisp could be a bit faster (Emacs is still faster for the
>>    Gabriel benchmarks), though I assume Guile will do better with code
>>    that uses lexical binding.
>
> This all sounds useful, but I was hoping for something that would get
> the project closer to Emacs integration.  Do you think anything can
> realistically be done in that respect, or is the above already enough
> work?

I think a logical next step would be to update Ken Raeburn's Guilemacs
patches to work with Emacs 24 and Guile 2.0, perhaps in parallel with
the above tasks. I'll include that in my proposal

> If the latter, would you be around after the summer to work on Emacs
> integration?  :-)

Yes. Porting the Generic Window Manager to Guile has been good practice
for that (:

amike,
BT
-- 
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:[~2011-04-06 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19 11:17 gnu in summer-of-code: more projects needed Andy Wingo
2011-04-04  7:41 ` BT Templeton
2011-04-04 21:20   ` Ludovic Courtès
2011-04-06 21:22     ` BT Templeton [this message]
2011-04-07 15:56       ` Ludovic Courtès

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=87fwpv6po5.fsf@olor.terpri.org \
    --to=bpt@hcoop.net \
    --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.
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).