From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org, gerd.moellmann@t-online.de (Gerd Moellmann)
Subject: Re: Why do we spend time on Emacs on Guile?
Date: 16 Aug 2002 12:36:17 -0400 [thread overview]
Message-ID: <jkn0rm69ry.fsf@glug.org> (raw)
In-Reply-To: storm@cua.dk's message of "16 Aug 2002 11:34:30 +0200"
storm@cua.dk (Kim F. Storm) writes:
How many of the members on emacs-devel plan to switch to Guile once
it is available?
if it's done right, guile availability won't require switching; it will
just Be There. of course, there are ways to Be quite ugly but that's
another question. it should always be possible to write elisp programs
and expect emacs to execute them.
Why would you do that?
for one thing, guile scheme object properties are very general (at
least, historically). most anything can be a property as well as a
value. it's easy to build trees w/ this kind of facility.
Have you ever programmed in Guile/Scheme ? How much?
check out http://www.glug.org/maint/ for ongoing travails... also
relevant to this list would be a google search for "gap-buffer.scm" and
in the same directory edit.scm. see gpgutils.scm for example usage of
edit.scm (warning: not suitable for either scheme or elisp purists ;-).
I doubt very many existing Emacs Lisp packages will be converted to
Guile, so what are the performance issues of not doing so if Emacs
uses Guile internally?
it used to be you could compile a large subset of guile scheme to a
shared object library (.so file) and of course load that. perhaps that
will be possible again in the future. see latest SCM by Aubrey Jaffer.
thi
next prev parent reply other threads:[~2002-08-16 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86y9b8awuv.fsf@gerd.free-bsd.org>
2002-08-16 9:34 ` Why do we spend time on Emacs on Guile? Kim F. Storm
2002-08-16 16:36 ` Thien-Thi Nguyen [this message]
2002-08-16 22:46 ` Werner LEMBERG
2002-08-17 23:28 ` Thien-Thi Nguyen
2002-08-16 16:52 ` D. Goel
2002-08-16 18:02 ` Sam Steingold
2002-08-17 4:50 ` Richard Stallman
2002-08-17 13:02 ` Sam Steingold
2002-08-23 7:02 ` Michael Sperber [Mr. Preprocessor]
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=jkn0rm69ry.fsf@glug.org \
--to=ttn@glug.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@t-online.de \
/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).