unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <christian.lynbech@tieto.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Andy Wingo <wingo@pobox.com>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: guile and emacs and elisp, oh my!
Date: Wed, 21 Apr 2010 09:37:55 +0200	[thread overview]
Message-ID: <ytqpbpdd8dd8.fsf@tieto.com> (raw)
In-Reply-To: <m3wrw1da4t.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed,  21 Apr 2010 01:36:34 +0300")

I think there are a number of benefits to rebasing Emacs Lisp to a more
commonly used platform, even if this will not be immediately visible to
the casual user, some of the more obvious (as already hashed out in the
other discussions):

   - If elisp is fast enough today, it is to some extent because *lots*
     of functionality has moved to the C world. A faster implementation
     (with a FFI) would allow to take more of the internals back and hence
     allow gerater flexbility and more room for improvement.

   - Developer resources are limited, teaming up with an existing
     platform will provide more hands on the internals and hence free up
     time for the emacs specific work.

   - Having access to a more widely used language will enable non-emacs
     libraries to be imported into emacs or emacs libraries to be used
     elsewhere. For instance the buffer abstraction is one that probaly
     is useful in a number of applications.

I am not able to say if standardizing on a single language platform
across the GNU project makes sense or not. It probably will be very
difficult to decide on one particular language but having a common
platform with multiple languages sitting on top at least will enable a
considerable amount of work to be shared among application development.

It will take time and energy to change the language machinery of Emacs
but we should not forget that a significant portion of that effort has
already been spent and that one also should not underestimate the effort
needed to make the needed high-quality extensions to Emacs Lisp on the
existing implementation and to maintain them afterwards across the vast
score of platforms on which Emacs runs today.


------------------------+-----------------------------------------------------
Christian Lynbech       | christian #\@ defun #\. dk
------------------------+-----------------------------------------------------
Hit the philistines three times over the head with the Elisp reference manual.
                                        - petonic@hal.com (Michael A. Petonic)




  reply	other threads:[~2010-04-21  7:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 20:18 guile and emacs and elisp, oh my! Andy Wingo
2010-04-15  8:38 ` christian.lynbech
2010-04-15  8:53 ` joakim
2010-04-15 17:34   ` Andy Wingo
2010-04-15 23:54   ` Ken Raeburn
2010-04-16  6:48     ` joakim
2010-04-16 17:05     ` Ken Raeburn
2010-04-16 17:16       ` Ken Raeburn
2010-04-16 18:23       ` Stefan Monnier
2010-04-20 22:36 ` Tom Tromey
2010-04-21  7:37   ` christian.lynbech [this message]
2010-04-21  9:27   ` David Engster
2010-04-21  9:49     ` David Kastrup
2010-04-21 11:04       ` Lennart Borgman
2010-04-21 11:58       ` David Engster
2010-04-21 12:22         ` David Kastrup
2010-04-21 16:43   ` Ludovic Courtès
2010-04-22  9:35   ` Andy Wingo
2010-04-22 15:14     ` Karl Fogel
2010-04-25 19:36       ` Tom Tromey
2010-04-23  2:00     ` Thomas Lord
2010-04-23  8:28       ` Andy Wingo
2010-04-23  9:17         ` Ludovic Courtès
2010-04-23 10:19         ` christian.lynbech
2010-04-23 11:28           ` Andy Wingo
2010-04-23 11:31             ` christian.lynbech
2010-04-23 13:10               ` Andy Wingo
2010-04-23 22:43         ` Thomas Lord
2010-04-24 11:05           ` Andy Wingo
2010-04-25  0:02             ` Thomas Lord
2010-04-25 16:54           ` Richard Stallman
2010-04-25 17:11             ` Andy Wingo

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=ytqpbpdd8dd8.fsf@tieto.com \
    --to=christian.lynbech@tieto.com \
    --cc=emacs-devel@gnu.org \
    --cc=tromey@redhat.com \
    --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.
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).