>>>"Hrvoje" == Hrvoje Niksic schrieb am 02 Jul 1998
11:36:38 +0200:
Hrvoje> To rephrase: current behaviour of `let' is by no means
Hrvoje> considered a feature. OK?
;-) Yes.
> We're arguing about probably having to change a lot of
_existing_
> Emacs Lisp code
Hrvoje> Only the code that bogusly uses special variables without
Hrvoje> declaring them as such. This code would probably be easy
Hrvoje> enough to fix (easier than ebola). Our byte-compiler even
Hrvoje> now warns of such code.
Well, if you just consider the Elisp currently at the Lisp archive or
the ones shipping with XEmacs, anything might be fine. But what about
the guys who have written their own private `foo'-package ? Force a
recompile and have them fix their surprisingly-now-buggy code which
has been legal elisp for years ?
Hrvoje> I don't care. Emacs is not ANSI CL. If that was the
Hrvoje> impression I was giving, I apologize, because that is not
Hrvoje> what I meant.
> But, what is then the point of substituting Emacs Lisp with
> another non-sense Lisp ?
Hrvoje> Why do you call non-sense anything that is not strictly ANSI
Hrvoje> conformant?
If you could tell me where the sense is of using some language (or
even worse: an implementation) not standarized when standarized
versions exist ... ?
But I didn't meant to be rude, I apologize for being too offensive.
> state-of-the-art RSR5-Scheme system. And, my favourite, if
> somebody wants to replace the existing lisp engine, go for a
> language engine that allows support for Emacs-Lisp, Common Lisp
> and Scheme (and perl or tcl, perhaps).
Hrvoje> Yeah, and Java and C++. Why not add SNOBOL, for good
Hrvoje> measure?
Haha. I was just thinking of the re-occuring threads in comp.emacs.*
but certainly won't want that for myself. But if the engine would be
able to support language X, and there is somebody who wants to
implement and use X, hey, who am I stopping him from doing so ?
Hrvoje> I did, but you weren't listening.
Nope, you were not. Do you want to replace Emacs Lisp with (a
substrate of a) Common Lisp (_implementation_) or do you want to two
concurrent lisp engines ? AFAIU, you want the former, but I'm by no
means sure.
[CMUCL]
Hrvoje> 17f coredumped on me even on trivial examples. :-(
I haven't read comp.lang.lisp for a while, and I haven't seen anybody
reporting problems (which of course doesn't mean that they don't
exist).
Holger
--
---
http://www.coling.uni-freiburg.de/~schauer ---
Why people hate using Lisp:
"Are people suffering from parenthophobia-by-proxy, mistaking
`parens' for `parents'?" - Erik Naggum in comp.emacs.xemacs