http://www.nocrew.org/news.html?article=115
http://www.lisp.se/emacs-cl/
Will it work with plisp? The following is an excerpt
http://www.nocrew.org/cgi-bin/cvsweb/cvsweb.cgi/emacs-cl/README?rev=1.23
There are problems with the cl:function macro when its output appears
in compiled files:
* When applied to a byte-code function the result will be printed
with the #[...] syntax. That works, but separate invokations of
cl:function will result in distinct, though equal, code vectors.
* When's applied to a subr, the result will be printed with the
#<subr ...> syntax, which will raise a syntax error when loaded.
In general, Emacs' byte compiler doesn't preserve object identity,
which is a problem.
From: Lars Brinkhoff
Subject: Re: postscript to lisp, plisp package error - Invalid read syntax: "#
Date:
Message-ID: <85lln2oykr.fsf@junk.nocrew.org>
Nomen Nescio <······@dizum.com> writes:
> http://www.lisp.se/emacs-cl/
> Will it work with plisp? The following is an excerpt
Probably not. Emacs Common Lisp is too buggy to work with anything
but trivial snippets of code.
--
Lars Brinkhoff, Services for Unix, Linux, GCC, HTTP
Brinkhoff Consulting http://www.brinkhoff.se/
Lars Brinkhoff <·········@nocrew.org> writes:
> Nomen Nescio <······@dizum.com> writes:
> > http://www.lisp.se/emacs-cl/
> > Will it work with plisp? The following is an excerpt
>
> Probably not. Emacs Common Lisp is too buggy to work with anything
> but trivial snippets of code.
Not a reason not to try! Let's people find these bugs and send you
patches! :-)
--
__Pascal_Bourguignon__ http://www.informatimago.com/
There is no worse tyranny than to force a man to pay for what he doesn't
want merely because you think it would be good for him.--Robert Heinlein
http://www.theadvocates.org/