Hello,
This function is not working in the latest ABCL version: http://clhs.lisp.se/Body/f_cmp.htm
This is what I get when I try to evaluate the example in CLHS:
(defun foo () "bar") => FOO
(compile 'foo)
Wrong number of arguments for #<FUNCTION {5236A94B}>. [Condition of type PROGRAM-ERROR]
Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread.
Backtrace: 0: (#<FUNCTION {752CC03}> #<PROGRAM-ERROR {600776A0}> #<FUNCTION {752CC03}>) 1: (APPLY #<FUNCTION {752CC03}> (#<PROGRAM-ERROR {600776A0}> #<FUNCTION {752CC03}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<PROGRAM-ERROR {600776A0}> #<FUNCTION {752CC03}>) 3: (INVOKE-DEBUGGER #<PROGRAM-ERROR {600776A0}>) 4: org.armedbear.lisp.Lisp.error(Lisp.java:382) 5: org.armedbear.lisp.CompiledClosure.notImplemented(CompiledClosure.java:81) 6: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:212) 7: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:121) 8: org.armedbear.lisp.FuncallableStandardObject.execute(FuncallableStandardObject.java:117) 9: org.armedbear.lisp.Symbol.execute(Symbol.java:826) 10: org.armedbear.lisp.compiler_pass2_387.execute(compiler-pass2.lisp:7495) 11: org.armedbear.lisp.compiler_pass2_370.execute(compiler-pass2.lisp:7450) 12: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:98) 13: org.armedbear.lisp.Symbol.execute(Symbol.java:803) 14: org.armedbear.lisp.compiler_pass2_386.execute(compiler-pass2.lisp:7495) 15: org.armedbear.lisp.Symbol.execute(Symbol.java:838) 16: org.armedbear.lisp.compiler_pass2_388.execute(compiler-pass2.lisp:7519) 17: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:109) 18: org.armedbear.lisp.Symbol.execute(Symbol.java:814) 19: org.armedbear.lisp.compiler_pass2_392.execute(compiler-pass2.lisp:7589) 20: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:98) 21: org.armedbear.lisp.LispThread.execute(LispThread.java:814) 22: org.armedbear.lisp.Lisp.evalCall(Lisp.java:575) 23: org.armedbear.lisp.Lisp.eval(Lisp.java:540) 24: org.armedbear.lisp.Primitives$pf__eval.execute(Primitives.java:345) 25: (COMPILE FOO)
I'm not using this directly, but some libraries like closer-mop, need compile to work.
Fails here:
CL-USER> (lisp-implementation-type) "Armed Bear Common Lisp" CL-USER> (lisp-implementation-version) "1.4.0-dev-svn-14713" "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.7.0_55-b14" "amd64-Linux-3.5.0-17-generic"
It seems to work in some cases on ABCL 1.3.1, though.
CL-USER> (compile 'foo) FOO NIL NIL
But something like this signals an error:
CL-USER> (compile nil '(lambda (x) x)) ; Evaluation aborted on #<PROGRAM-ERROR {4C62C417}>.
With the same error above.
CL-USER> (lisp-implementation-version) "1.3.1" "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.7.0_55-b14" "amd64-Linux-3.5.0-17-generic"
I couldn't put this on the bugs tracker because I don't have permissions.
Cheers,
Mariano
_______________________________________________ Armedbear-devel mailing list Armedbear-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
On Jun 19, 2014, at 17:36, Mariano Montone marianomontone@gmail.com wrote:
[…]
This function is not working in the latest ABCL version: http://clhs.lisp.se/Body/f_cmp.htm
[…]
I'm not using this directly, but some libraries like closer-mop, need compile to work.
I really dont know what to make of your report as CL:COMPILE works fine on my end, including its usage within CLOSER-MOP, with both abcl-1.3.1 and SVN trunk.
Anybody else have ideas?
[…]
I couldn't put this on the bugs tracker because I don't have permissions.
You can sign in with an [OpenID][], such a Google or Yahoo! account.
[OpenID]: https://en.wikipedia.org/wiki/OpenID
Thanks for looking into this. I will try to figure out what is wrong in my setup
On 20 de junio de 2014 3:56:47 GMT-03:00, Mark Evenson evenson@panix.com wrote:
On Jun 19, 2014, at 17:36, Mariano Montone marianomontone@gmail.com wrote:
[…]
This function is not working in the latest ABCL version: http://clhs.lisp.se/Body/f_cmp.htm
[…]
I'm not using this directly, but some libraries like closer-mop, need compile to work.
I really dont know what to make of your report as CL:COMPILE works fine on my end, including its usage within CLOSER-MOP, with both abcl-1.3.1 and SVN trunk.
Anybody else have ideas?
[…]
I couldn't put this on the bugs tracker because I don't have
permissions.
You can sign in with an [OpenID][], such a Google or Yahoo! account.
-- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."
Ok. I've tried again before loading my application, and it is working. So it must be a package I'm loading that somehow messes up.
On Fri, Jun 20, 2014 at 10:24 AM, Mariano Montone marianomontone@gmail.com wrote:
Thanks for looking into this. I will try to figure out what is wrong in my setup
On 20 de junio de 2014 3:56:47 GMT-03:00, Mark Evenson evenson@panix.com wrote:
On Jun 19, 2014, at 17:36, Mariano Montone marianomontone@gmail.com wrote:
[…]
This function is not working in the latest ABCL version:
[…]
I'm not using this directly, but some libraries like closer-mop, need compile to work.
I really dont know what to make of your report as CL:COMPILE works fine on my end, including its usage within CLOSER-MOP, with both abcl-1.3.1 and SVN trunk.
Anybody else have ideas?
[…]
I couldn't put this on the bugs tracker because I don't have permissions.
You can sign in with an [OpenID][], such a Google or Yahoo! account.
armedbear-devel@common-lisp.net