From: MON KEY <monkey@sandpframing.com>
To: emacs-devel@gnu.org
Cc: stephen@xemacs.org
Subject: Re: Return
Date: Sun, 5 Dec 2010 18:55:18 -0500 [thread overview]
Message-ID: <AANLkTin0mwUk-OzWRYEDbomFBSPBjC9WhyiaYxz-MUGJ@mail.gmail.com> (raw)
,----
| Note that Python (at least) has adopted this approach, with a core
| language definition that is 99% or so independent of implementation
| (cf. CPython, Cython nee pyrex, Stackless Python, Jython, IronPython,
| and PyPy).
`----
Pshaw... Doesn't GVR eschew ++Lambda++ in p3k? Heresy!
,----
| Speaking of Common Lisp, since it has a package scheme, you might be
| able to implement the elisp interpreter by using the elisp
| interpreter, and put in in a package that uses elisp eval instead of
| Common Lisp's eval.
`----
Sam Steingold has explored this in the CLOCC.
There is also LICE.
Pretty sure Closure has an "Emacs like" editor for Mac environs.
PJB maintains quite a bit of Elisp<-->Common-Lisp code.
FWIW I've been collecting various bits and pieces from the above mentioned
sources into a personal package for the last ~6 months.
I'm sure many Common Lispers do similarly.
Also, as mentioned there is Climacs which is quite functional with McClim/CLX.
Likewise, there is Hemlock. (AIUI someone is currently porting it to Qt...)
Also, there are any number of legacy "Emacs like" editors from the
Lispm/TI/Symbolics/BBN/Xerox... implementations. Source is generally available
for all of these.
Contemporary commercial sources like Lispworks and Allegro provide "Emacs like"
editors.
Given Emacs' Maclisp lineage and the number of Lisp2 users whom actively use
GNU/Xemacs (or some equivalent) and the presence of a formal Common Lisp
specification implemented on myriad platforms and multiple
implementations of said
specification, why on earth should a switch to either a Scheme/Python VM warrant
consideration.
FWIW I find it quite odd that discussions of moving the Emacs VM to
Guile are bandied
about when Clisp is available as a GNU project (since forever), has an existing
C interface, is easily as portable across platformas as Guile scheme, counts
among its core authors a formidable contributor to various high-level
GNU projects
(Bruno Haible) and has the admirable quality that it doesn't get confused
between nil/empty-list/falsehood in the way that a Scheme will.
--
/s_P\
next reply other threads:[~2010-12-05 23:55 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 23:55 MON KEY [this message]
2010-12-06 1:48 ` Return Stephen J. Turnbull
2010-12-06 5:50 ` Return MON KEY
2010-12-06 7:20 ` Return Stephen J. Turnbull
2010-12-06 9:00 ` Return David Kastrup
2010-12-06 19:11 ` Return Stefan Monnier
2010-12-06 19:09 ` Return Stefan Monnier
2010-12-06 19:19 ` Return Chong Yidong
2010-12-06 20:27 ` Return Stefan Monnier
2010-12-07 4:47 ` Return Miles Bader
2010-12-07 9:17 ` Return David Kastrup
2010-12-07 17:10 ` Return Stefan Monnier
2010-12-07 22:15 ` Return David Kastrup
2010-12-08 15:50 ` Return Fren Zeee
2010-12-09 22:38 ` Return Stefan Monnier
2010-12-10 1:41 ` Return Stephen J. Turnbull
2010-12-10 3:44 ` Return Stefan Monnier
2010-12-10 8:28 ` Return Stephen J. Turnbull
2010-12-23 5:39 ` Return Fren Zeee
2010-12-07 12:44 ` Return Stephen J. Turnbull
2010-12-07 14:38 ` Return David Kastrup
2010-12-07 16:14 ` Return Stephen J. Turnbull
2010-12-07 17:11 ` Return tomas
2010-12-07 2:42 ` Return MON KEY
2010-12-07 14:34 ` Return Stephen J. Turnbull
2010-12-07 15:54 ` Return David Kastrup
2010-12-07 16:30 ` Return Stephen J. Turnbull
2010-12-08 13:42 ` Return Richard Stallman
2010-12-10 7:42 ` Return Daniel Colascione
2010-12-10 8:53 ` Keyword args (was: Return) Helmut Eller
2010-12-13 2:10 ` Keyword args Daniel Colascione
2010-12-13 8:30 ` Helmut Eller
2010-12-13 20:00 ` Andy Wingo
2010-12-14 5:03 ` Miles Bader
2010-12-14 7:43 ` Helmut Eller
2010-12-07 22:55 ` Return MON KEY
2010-12-08 7:28 ` Return Stephen J. Turnbull
2010-12-08 18:11 ` Return MON KEY
2010-12-09 8:37 ` Return Stephen J. Turnbull
2010-12-07 23:21 ` Return Samuel Bronson
2010-12-08 8:06 ` Return Stephen J. Turnbull
2010-12-08 20:51 ` Return Samuel Bronson
-- strict thread matches above, loose matches on Subject: below --
2010-11-26 23:01 return MON KEY
2010-11-26 8:57 return Lars Magne Ingebrigtsen
2010-11-26 9:19 ` return Tassilo Horn
2010-12-04 2:36 ` return Fren Zeee
2010-12-04 6:18 ` return Stephen J. Turnbull
2010-12-04 6:49 ` return Leo
2010-11-26 9:24 ` return Miles Bader
2010-11-26 9:36 ` return Lars Magne Ingebrigtsen
2010-11-26 9:54 ` return Miles Bader
2010-11-26 10:13 ` return Lars Magne Ingebrigtsen
2010-11-26 9:44 ` return Tassilo Horn
2010-11-26 14:59 ` return Stefan Monnier
2010-11-26 15:45 ` return Lars Magne Ingebrigtsen
2010-11-26 18:40 ` return Stefan Monnier
2010-11-27 1:31 ` return Lars Magne Ingebrigtsen
2010-11-27 2:49 ` return Stefan Monnier
2010-11-27 3:06 ` return Lars Magne Ingebrigtsen
2010-12-03 18:41 ` return Chong Yidong
2010-12-03 18:43 ` return Miles Bader
2010-12-03 19:46 ` return Chong Yidong
2010-12-03 21:26 ` return Chong Yidong
2010-12-03 22:29 ` return Stefan Monnier
2010-12-03 23:00 ` return Chong Yidong
2010-12-04 1:35 ` return Stefan Monnier
2010-12-04 3:23 ` return Chong Yidong
2010-12-06 16:13 ` return Davis Herring
2010-12-06 17:15 ` return Chong Yidong
2010-12-03 22:44 ` return Chong Yidong
2010-12-04 9:22 ` return Helmut Eller
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=AANLkTin0mwUk-OzWRYEDbomFBSPBjC9WhyiaYxz-MUGJ@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).