[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs Lisp's future
|
From: |
Lars Brinkhoff |
|
Subject: |
Re: Emacs Lisp's future |
|
Date: |
Wed, 17 Sep 2014 18:57:32 +0200 |
|
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
> Compiling from CL to Elisp means that the two aren't integrated, so
> calling code from one to the other is not seamless.
I don't know why you say that. In my implementation it's currently
not entirely seamless, but close, and I can easily imagine ways to
make it so.
But anyway, this is not the time nor the place to discuss that. It's
not really relevant to what you wrote about Emacs Lisp's future.
Sorry for the noise.
- Guile emacs thread (again), Christopher Allan Webber, 2014/09/13
- Re: Guile emacs thread (again), Eli Zaretskii, 2014/09/14
- Re: Guile emacs thread (again), Grim Schjetne, 2014/09/16
- Emacs Lisp's future (was: Guile emacs thread (again)), Stefan Monnier, 2014/09/16
- Re: Emacs Lisp's future, David Kastrup, 2014/09/16
- Re: Emacs Lisp's future, Mark H Weaver, 2014/09/17
- Re: Emacs Lisp's future, Mark H Weaver, 2014/09/17
- Re: Emacs Lisp's future, David Kastrup, 2014/09/17
- Re: Emacs Lisp's future, Mark H Weaver, 2014/09/17
- Re: Emacs Lisp's future, David Kastrup, 2014/09/17
- Re: Emacs Lisp's future, Nic Ferrier, 2014/09/17
- Re: Emacs Lisp's future, mhw, 2014/09/17
- Re: Emacs Lisp's future, David Kastrup, 2014/09/17
- Re: Emacs Lisp's future, Mark H Weaver, 2014/09/17