May 2012 - armedbear-ticket - mailman3.common-lisp.net

[armedbear-ticket] [armedbear] #208: Files loaded via "--load <FILE>" on the command line have no pathname defaults
by armedbear 14 Aug '12

14 Aug '12

#208: Files loaded via "--load <FILE>" on the command line have no pathname defaults -------------------------+-------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: 1.1.0 Component: interpreter | Version: 1.1.0-dev Keywords: | -------------------------+-------------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2291 Wei-Lun Chiu reports] {{{ I have a file: ---- load-pathname.lisp ----- (print *load-pathname*) ----------------------------- When loaded, I get this: java.exe -cp "abcl.jar" org.armedbear.lisp.Main --load load-path.lisp==> #P"load-path.lisp" According to CLHS, I believe this is wrong? During a call to load, *load-pathname* is bound to the pathname denoted by the the first argument to load, merged against the defaults; that is, it is bound to (pathname (merge-pathnames filespec)). }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/208> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

[armedbear-ticket] [armedbear] #176: Patch to get CFFI to find the JNA libraries dynamically via Maven3
by armedbear 13 Aug '12

13 Aug '12

#176: Patch to get CFFI to find the JNA libraries dynamically via Maven3 ----------------------------+----------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: unscheduled Component: libraries | Version: Keywords: quicklisp cffi | ----------------------------+----------------------------------------------- Need to get the following upstream to CFFI to ease use of JNA: {{{ #+abcl (eval-when (:load-toplevel) (require 'abcl-contrib) (require 'abcl-asdf) (java:add-to-classpath (abcl-asdf:resolve-dependencies "com.sun.jna" "jna" "3.0.9"))) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/176> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

[armedbear-ticket] [armedbear] #195: prompt is displayed twice when evaluating NIL at the REPL
by armedbear 11 Aug '12

11 Aug '12

#195: prompt is displayed twice when evaluating NIL at the REPL -------------------------+-------------------------------------------------- Reporter: rschlatte | Owner: ehuelsmann Type: defect | Status: new Priority: trivial | Milestone: Component: interpreter | Version: Keywords: | -------------------------+-------------------------------------------------- {{{ $ abcl Armed Bear Common Lisp 1.1.0-dev Java 1.6.0_29 Apple Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.724 seconds. Startup completed in 2.336 seconds. Loading /home/rudi/.abclrc completed in 11.57 seconds. Type ":help" for a list of available commands. CL-USER(1): NIL NIL CL-USER(2): CL-USER(2): }}} Reported by Blake McBride Jan 16, 2012 -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/195> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #168: Compilation fails for quicklisp let-plus
by armedbear 08 Aug '12

08 Aug '12

#168: Compilation fails for quicklisp let-plus ----------------------------------------+----------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 0.28 Component: compiler | Version: Keywords: quicklisp ansi_confromance | ----------------------------------------+----------------------------------- let-plus-20110730-git, a dependency for LLA, cannot be compiled resulting in the following error: {{{ ; Loading /Users/evenson/.cache/common-lisp/abcl-0.27.0-dev-fasl37-macosx- java/Users/evenson/quicklisp/dists/quicklisp/software/let- plus-20110730-git/package.abcl ... ; Loaded /Users/evenson/.cache/common-lisp/abcl-0.27.0-dev-fasl37-macosx- java/Users/evenson/quicklisp/dists/quicklisp/software/let- plus-20110730-git/package.abcl (0.027 seconds) ; Compiling /Users/evenson/quicklisp/dists/quicklisp/software/let- plus-20110730-git/let-plus.lisp ... ; (IN-PACKAGE #:LET-PLUS) ; (DEFUN IGNORED? ...) ; (DEFUN REPLACE-IGNORED ...) ; (DEFUN EXPAND-SLOT-FORMS ...) ; (DEFUN EXPAND-ENTRY-FORMS ...) ; (DEFUN EXPAND-ARRAY-ELEMENTS ...) ; (DEFGENERIC LET+-EXPANSION ...) ; (DEFGENERIC LET+-EXPANSION-FOR-LIST ...) ; (DEFMACRO LET+ ...) ; (DEFMACRO DEFINE-LET+-EXPANSION ...) #<THREAD "interpreter" {52BBC66F}>: Debugger invoked on condition of type COMPILER-UNSUPPORTED-FEATURE-ERROR COMPILE-FORM unhandled case ((ANAPHORA:IT #:THIS-S2842)) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/168> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 6

[armedbear-ticket] [armedbear] #73: "normalize-type" buffering
by armedbear 08 Aug '12

08 Aug '12

#73: "normalize-type" buffering -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: task | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: performance | -------------------------+-------------------------------------------------- Peter Graves points out that with his "canonicalize-type" buffering, he achieved measurable performance gain in XCL. We want to do the same in ABCL. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/73> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #202: ENSURE-GENERIC-FUNCTION assumes LAMBDA-LIST is NIL
by armedbear 06 Aug '12

06 Aug '12

#202: ENSURE-GENERIC-FUNCTION assumes LAMBDA-LIST is NIL --------------------+------------------------------------------------------- Reporter: gpfeil | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: Component: (A)MOP | Version: 1.1.0-dev Keywords: | --------------------+------------------------------------------------------- I know ABCL's MOP isn't complete yet, but I just saw this with ENSURE- GENERIC-FUNCTION. {{{ (ensure-generic-function 'make-instance :method-combination *contract-method- combination*) }}} complains that the lambda list NIL isn't compatible with MAKE-INSTANCE's lambda list. If I don't pass the :LAMBDA-LIST parameter, it shouldn't attempt to change the lambda list. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/202> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #201: &WHOLE broken in DEFINE-METHOD-COMBINATION
by armedbear 05 Aug '12

05 Aug '12

#201: &WHOLE broken in DEFINE-METHOD-COMBINATION ----------------------------------------------------------------------------------------------+ Reporter: https://www.google.com/accounts/o8/id?id=aitoawlfp20ohzeq8vs4btepsaqltprtai… | Owner: somebody Type: defect | Status: new Priority: minor | Milestone: Component: CLOS | Version: 1.1.0-dev Keywords: | ----------------------------------------------------------------------------------------------+ I get an error whenever I call a function that uses the simple method combination shown here. {{{ CL-USER> (define-method-combination progn-with-whole () ((methods ())) (:arguments &whole whole) `(progn (format nil "using ~a" ,whole) ,@(mapcar (lambda (method) `(call-method ,method)) methods))) PROGN-WITH-WHOLE CL-USER> (defgeneric test-&whole (x) (:method-combination progn-with-whole) (:method (x) x)) #<STANDARD-GENERIC-FUNCTION TEST-&WHOLE {34315D04}> CL-USER> (test-&whole 4) }}} Here is the error: {{{ The value 4 is not of type LIST. [Condition of type TYPE-ERROR] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {C69203}> #<TYPE-ERROR {FE85ADF}> #<FUNCTION {C69203}>) 1: (APPLY #<FUNCTION {C69203}> (#<TYPE-ERROR {FE85ADF}> #<FUNCTION {C69203}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<TYPE-ERROR {FE85ADF}> #<FUNCTION {C69203}>) 3: (INVOKE-DEBUGGER #<TYPE-ERROR {FE85ADF}>) 4: org.armedbear.lisp.Lisp.error(Lisp.java:379) 5: org.armedbear.lisp.Lisp.type_error(Lisp.java:420) 6: org.armedbear.lisp.LispObject.car(LispObject.java:156) 7: org.armedbear.lisp.Lisp.eval(Lisp.java:520) 8: org.armedbear.lisp.Lisp.evalCall(Lisp.java:559) 9: org.armedbear.lisp.Lisp.eval(Lisp.java:515) 10: org.armedbear.lisp.Lisp.progn(Lisp.java:684) 11: org.armedbear.lisp.SpecialOperators$sf_progn.execute(SpecialOperators.java:275) 12: org.armedbear.lisp.Lisp.eval(Lisp.java:505) 13: org.armedbear.lisp.Lisp.progn(Lisp.java:684) 14: org.armedbear.lisp.Primitives$sf_macrolet.execute(Primitives.java:3641) 15: ((LAMBDA (#:G13665) (MACROLET (#) (PROGN # #))) (4)) 16: (FUNCALL (LAMBDA (#:G13665) (MACROLET (#) (PROGN # #))) (4)) 17: (#<STANDARD-GENERIC-FUNCTION TEST-&WHOLE {34315D04}> 4) 18: (APPLY #<STANDARD-GENERIC-FUNCTION TEST-&WHOLE {34315D04}> (4)) 19: (MOP::INITIAL-DISCRIMINATING-FUNCTION #<STANDARD-GENERIC-FUNCTION TEST-&WHOLE {34315D04}> (4)) 20: (#<STANDARD-GENERIC-FUNCTION TEST-&WHOLE {34315D04}> 4) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/201> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #175: abcl.release target fails occasionally
by armedbear 29 Jul '12

29 Jul '12

#175: abcl.release target fails occasionally --------------------------+------------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: 1.0 Component: build | Version: 0.27 Keywords: abcl.release | --------------------------+------------------------------------------------- The central abcl.release target can fail unpredictably, so it is current best to clean the intermediate build targets before making a release. 'abcl.release' currently *always* fails under MSFT Windows. @erik had noted this in #abcl. http://trac.common-lisp.net/armedbear/changeset/12419 -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/175> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 7

[armedbear-ticket] [armedbear] #60: Implement USE-FAST-CALLS properly
by armedbear 29 Jul '12

29 Jul '12

#60: Implement USE-FAST-CALLS properly -------------------------+-------------------------------------------------- Reporter: trittweiler | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: Component: compiler | Version: Keywords: | -------------------------+-------------------------------------------------- USE-FAST-CALLS is implemented at the moment by flipping an essentially global variable. The proper implementation would be to make turn it into a ABCL-specific declaration, and making sure it affects its lexically enclosing code only. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/60> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #206: COMPILER-UNSUPPORTED-FEATURE-ERROR is derived from condition, rather than from ERROR
by armedbear 29 Jul '12

29 Jul '12

#206: COMPILER-UNSUPPORTED-FEATURE-ERROR is derived from condition, rather than from ERROR ----------------------------------------------------------------------------------------------+ Reporter: https://www.google.com/accounts/o8/id?id=aitoawmcq6mzgezjmpqv2tjhvs6isymf6t… | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: Component: compiler | Version: Keywords: | ----------------------------------------------------------------------------------------------+ Hello. My coade loads some ASDF systems, and wraps the asdf:operate call into handler-case {{{ (handler-case (asdf:operate ...) (serious-condition (condition) (... }}} This should help me to handle the build errors. But when I load the let-plus library, ABCL falls into debugger: {{{ #<THREAD "interpreter" {53B73EA7}>: Debugger invoked on condition of type COMPILER-UNSUPPORTED-FEATURE-ERROR COMPILE-FORM unhandled case ((ANAPHORA:IT #:THIS-S100224)) Restarts: 0: RETRY Retry compiling #<ASDF:CL-SOURCE-FILE "let-plus" "let-plus">. 1: ACCEPT Continue, treating compiling #<ASDF:CL-SOURCE-FILE "let-plus" "let-plus"> as having been successful. 2: ABORT Give up on "let-plus" [1] LET-PLUS(1): 0 }}} This happens because COMPILER-UNSUPPORTED-FEATURE-ERROR is derived from CONDITION (see src/org/armedbear/lisp/CompilerUnsupportedFeatureError.java) CLHS says: "Conditions of type error might be signaled by the compiler in situations where the compilation cannot proceed without intervention." http://www.lispworks.com/documentation/lw51/CLHS/Body/03_be.htm It would be better to derive COMPILER-UNSUPPORTED-FEATURE-ERROR from ERROR (or at least from SERIOUS-CONDITION) - Anton Vodonosov -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/206> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #191: Compiling SHARPSIGN SHARPSIGN form causes stack overflow
by armedbear 28 Jul '12

28 Jul '12

#191: Compiling SHARPSIGN SHARPSIGN form causes stack overflow ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.0.1 Component: compiler | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2142 Anton reports] that compiling the alexandria tests from Quicklisp 2011-12-03 results in a stack overflow. The offending form seems to be {{{ (deftest circular-tree-p.2 (alexandria:circular-tree-p '#1=(#1#)) t) }}} where the problem seems to occur in the compiling ADD-ENTRY function {{{ 0: (#<FUNCTION {47D2FBB5}> #<STORAGE-CONDITION {18010D30}> #<FUNCTION {47D2FBB5}>) 1: (APPLY #<FUNCTION {47D2FBB5}> (#<STORAGE-CONDITION {18010D30}> #<FUNCTION {47D2FBB5}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<STORAGE-CONDITION {18010D30}> #<FUNCTION {47D2FBB5}>) 3: (INVOKE-DEBUGGER #<STORAGE-CONDITION {18010D30}>) […] 31: org.armedbear.lisp.Primitives$pf_apply.execute(Primitives.java:2853) 32: (#<FUNCTION {5F4298A5}>) 33: (JRUN-EXCEPTION-PROTECTED #<FUNCTION {5F4298A5}>) 34: (SYSTEM::CONVERT-TOPLEVEL-FORM (REGRESSION-TEST::ADD-ENTRY (REGRESSION-TEST::MAKE-ENTRY :PEND T :NAME 'ALEXANDRIA-TESTS::CIRCULAR- TREE-P.2 :PROPS ...)) NIL) 35: (SYSTEM::PROCESS-TOPLEVEL-FORM (REGRESSION-TEST::ADD-ENTRY (REGRESSION-TEST::MAKE-ENTRY :PEND T :NAME 'ALEXANDRIA-TESTS::CIRCULAR- TREE-P.2 :PROPS ...)) #<FILE-STREAM {D33A97F}> NIL) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/191> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 4

[armedbear-ticket] [armedbear] #32: Modify the currently disabled runtime-class.lisp code to not require ASM
by armedbear 28 Jul '12

28 Jul '12

#32: Modify the currently disabled runtime-class.lisp code to not require ASM --------------------------------------------------------------------+------- Reporter: vvoutilainen | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: jvm bytecode compiler runtime dynamic class generation | --------------------------------------------------------------------+------- It's possible to define classes at runtime, by generating bytecode and loading it from the generated binary data, without ever writing it to a temporary file. runtime-class.lisp does that, but it requires an external bytecode library (ASM). ABCL has all the functionality for this to be done without ASM, so the task is to modify the runtime-class.lisp code so that ASM is no longer required and the code can be taken to be part of the build. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/32> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #137: CLtL2 environment support
by armedbear 28 Jul '12

28 Jul '12

#137: CLtL2 environment support -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: enhancement | Status: new Priority: minor | Milestone: Component: compiler | Version: Keywords: | -------------------------+-------------------------------------------------- Cyrus Harmon requests support for [http://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node102.html#SECTION001250000… CLtL2 environment] objects support for his pixel access library, as described in a [http://cyrusharmon.org/blog/display?id=113 recent blog post] on [https://github.com/slyrus/opticl/blob/master/opticl.lisp opticl]. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/137> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #55: Clearing LispThread.currentThread()._values more efficiently
by armedbear 28 Jul '12

28 Jul '12

#55: Clearing LispThread.currentThread()._values more efficiently -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: enhancement | Status: new Priority: major | Milestone: Component: compiler | Version: Keywords: | -------------------------+-------------------------------------------------- We currently clear _values all over the place; we could be more efficient some times. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/55> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 8

[armedbear-ticket] [armedbear] #192: ASDF::IMPLEMENTATION-IDENTIFIER contains information on which ABCL was compiled
by armedbear 28 Jul '12

28 Jul '12

#192: ASDF::IMPLEMENTATION-IDENTIFIER contains information on which ABCL was compiled ------------------------------+--------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: trivial | Milestone: unscheduled Component: (A)MOP | Version: 1.0 Keywords: asdf, bite-sized | ------------------------------+--------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2169 Anton Vodonosov reports on armedbear-develop@] that the ASDF IMPLEMETATION-IDENTIFIER contains a reference to the system that ABCL was compiled on: For the [http://common-lisp.net/project/armedbear/release- notes-1.0.1.shtml Recent abcl-1.0.1 release] which was compiled on [http://wiki.openindiana.org/oi/oi_151a+Release+Notes OpenIndiana oi_151a] system one sees: {{{ CL-USER> (asdf::implementation-identifier) abcl-1.0.1-svn-13750-13751-fasl38-solaris-x86 }}} I vaguely remember discussing this with Faré, suggesting the right value might be the current JVM version that ABCL finds itself hosted upon. Patches solicited. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/192> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #34: adjust generated '*.cls' filenames
by armedbear 14 Jul '12

14 Jul '12

#34: adjust generated '*.cls' filenames ------------------------+--------------------------------------------------- Reporter: mevenson | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | ------------------------+--------------------------------------------------- dmiles: it be nice to eventually name the coerce-666.cls coerce_666.cls as the same name of the way classpaths think about them (they'd continue to work).. one argument agaist is our autoloader at least gets a better whack at finding them in the right context apart from classloader -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/34> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #173: Cannot initialize ABCL within .ear
by armedbear 30 May '12

30 May '12

#173: Cannot initialize ABCL within .ear -----------------------------------------------------------------------+---- Reporter: https://me.yahoo.com/a/KvgfiPIMkNAd1zTHUTfXlVJkp92K#3d978 | Owner: ehuelsmann Type: defect | Status: new Priority: blocker | Milestone: Component: interpreter | Version: 0.27 Keywords: | -----------------------------------------------------------------------+---- Exception is java.lang.Error: ABCL Debug.assertTrue() assertion failed! at org.armedbear.lisp.Debug.assertTrue(Debug.java:46) at org.armedbear.lisp.Pathname.init(Pathname.java:404) at org.armedbear.lisp.Pathname.<init>(Pathname.java:217) at org.armedbear.lisp.Site.init(Site.java:60) at org.armedbear.lisp.Site.getLispHome(Site.java:74) Truncated. see log file for complete stacktrace ABCL is initialized from .ear and tries to load boot.lisp on URL zip:/opt/was/.........abcl-0.27.0.jar!/......../boot.lisp -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/173> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 12

[armedbear-ticket] [armedbear] #210: Add JFLI to contrib
by armedbear 29 May '12

29 May '12

#210: Add JFLI to contrib -------------------------------+-------------------------------------------- Reporter: mevenson | Owner: mevenson Type: enhancement | Status: new Priority: major | Milestone: 1.1.0 Component: libraries | Version: Keywords: jfli abcl-contrib | -------------------------------+-------------------------------------------- Include Rich Hickey's JFLI in ABCL-CONTRIB Alex notes that he has possible additional patches. https://gist.github.com/avodonosov/abcl-idea/blob/master/src/abclidea/lisp /jfli-abcl/jfli-abcl.lisp -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/210> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #194: ansi-compiled CL-TEST::LOOP-16 test has stack overflow on java7
by armedbear 24 May '12

24 May '12

#194: ansi-compiled CL-TEST::LOOP-16 test has stack overflow on java7 ---------------------------------+------------------------------------------ Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: unscheduled Component: compiler | Version: 1.0.1 Keywords: java7 ansi-compiled | ---------------------------------+------------------------------------------ {{{ Stack overflow. [Condition of type STORAGE-CONDITION] Restarts: 0: [RETRY] Retry #<STANDARD-CLASS ASDF:TEST-OP {3EF04B6}> on #<ASDF:SYSTEM "ansi-compiled">. 1: [ACCEPT] Continue, treating #<STANDARD-CLASS ASDF:TEST-OP {3EF04B6}> on #<ASDF:SYSTEM "ansi-compiled"> as having been successful. 2: [ABORT] Abort compilation. 3: [*ABORT] Return to SLIME's top level. 4: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {17A4682F}> #<STORAGE-CONDITION {2AB3F1C9}> #<FUNCTION {17A4682F}>) 1: (APPLY #<FUNCTION {17A4682F}> (#<STORAGE-CONDITION {2AB3F1C9}> #<FUNCTION {17A4682F}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<STORAGE-CONDITION {2AB3F1C9}> #<FUNCTION {17A4682F}>) 3: (INVOKE-DEBUGGER #<STORAGE-CONDITION {2AB3F1C9}>) 4: org.armedbear.lisp.Lisp.error(Lisp.java:379) 5: org.armedbear.lisp.Java$pf_jrun_exception_protected.execute(Java.java:1315) 6: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 7: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 8: org.armedbear.lisp.rt_63.execute(rt.lsp:228) 9: org.armedbear.lisp.rt_67.execute(rt.lsp:228) 10: org.armedbear.lisp.LispThread.execute(LispThread.java:633) 11: org.armedbear.lisp.Java$pf_jrun_exception_protected.execute(Java.java:1308) 12: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 13: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 14: org.armedbear.lisp.rt_62.execute(rt.lsp:228) 15: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:112) 16: org.armedbear.lisp.Symbol.execute(Symbol.java:813) 17: org.armedbear.lisp.LispThread.execute(LispThread.java:666) 18: org.armedbear.lisp.rt_78.execute(rt.lsp:348) 19: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 20: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 21: org.armedbear.lisp.rt_77.execute(rt.lsp:335) 22: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:92) 23: org.armedbear.lisp.LispThread.execute(LispThread.java:633) 24: org.armedbear.lisp.Lisp.evalCall(Lisp.java:544) 25: org.armedbear.lisp.Lisp.eval(Lisp.java:515) 26: org.armedbear.lisp.Lisp.progn(Lisp.java:684) 27: org.armedbear.lisp.Closure.execute(Closure.java:426) 28: org.armedbear.lisp.Time$1.execute(Time.java:56) 29: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 30: org.armedbear.lisp.Lisp.evalCall(Lisp.java:550) 31: org.armedbear.lisp.Lisp.eval(Lisp.java:515) 32: org.armedbear.lisp.Lisp.eval(Lisp.java:508) 33: org.armedbear.lisp.Load.loadStream(Load.java:570) 34: org.armedbear.lisp.Load.loadFileFromStream(Load.java:526) 35: org.armedbear.lisp.Load.load(Load.java:201) 36: org.armedbear.lisp.Load.load(Load.java:686) 37: org.armedbear.lisp.Load$_load.execute(Load.java:636) 38: org.armedbear.lisp.Symbol.execute(Symbol.java:837) 39: org.armedbear.lisp.LispThread.execute(LispThread.java:701) 40: org.armedbear.lisp.load_1.execute(load.lisp:33) 41: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:101) 42: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 43: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 44: org.armedbear.lisp.ASDF_TMP_package_5.execute(package.lisp:22) 45: org.armedbear.lisp.Time$1.execute(Time.java:56) 46: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 47: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 48: org.armedbear.lisp.ASDF_TMP_package_1.execute(package.lisp:22) 49: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:112) 50: org.armedbear.lisp.Symbol.execute(Symbol.java:813) 51: org.armedbear.lisp.LispThread.execute(LispThread.java:666) 52: org.armedbear.lisp.Primitives$pf_funcall.execute(Primitives.java:2710) 53: (JRUN-EXCEPTION-PROTECTED #<FUNCTION {18E070C}>) 54: (#<FUNCTION {1370A5A0}>) 55: (JRUN-EXCEPTION-PROTECTED #<FUNCTION {1370A5A0}>) 56: (REGRESSION-TEST::DO-ENTRY #S(REGRESSION-TEST::ENTRY :PEND T :NAME CL-TEST::CLASS-07.2 :PROPS NIL :FORM (LET ((CL-TEST::C #)) (VALUES (CL- TEST::NOTNOT #) (CL-TEST::S1 CL-TEST::C) (SLOT-BOUNDP CL-TEST:.. Locals: "??" = "??" 57: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 58: abcl_211bc8a2_78e5_4d5d_b332_2512480e939c.execute(Unknown Source) 59: org.armedbear.lisp.LispThread.execute(LispThread.java:633) 60: org.armedbear.lisp.rt_64.execute(rt.lsp:228) 61: org.armedbear.lisp.LispThread.execute(LispThread.java:633) 62: org.armedbear.lisp.Java$pf_jrun_exception_protected.execute(Java.java:1308) 63: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 64: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 65: org.armedbear.lisp.rt_63.execute(rt.lsp:228) 66: org.armedbear.lisp.rt_67.execute(rt.lsp:228) 67: org.armedbear.lisp.LispThread.execute(LispThread.java:633) 68: org.armedbear.lisp.Java$pf_jrun_exception_protected.execute(Java.java:1308) 69: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 70: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 71: org.armedbear.lisp.rt_62.execute(rt.lsp:228) 72: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:112) 73: org.armedbear.lisp.Symbol.execute(Symbol.java:813) 74: org.armedbear.lisp.LispThread.execute(LispThread.java:666) 75: org.armedbear.lisp.rt_78.execute(rt.lsp:348) 76: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 77: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 78: org.armedbear.lisp.rt_77.execute(rt.lsp:335) 79: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:92) 80: org.armedbear.lisp.LispThread.execute(LispThread.java:633) 81: org.armedbear.lisp.Lisp.evalCall(Lisp.java:544) 82: org.armedbear.lisp.Lisp.eval(Lisp.java:515) 83: org.armedbear.lisp.Lisp.progn(Lisp.java:684) 84: org.armedbear.lisp.Closure.execute(Closure.java:426) 85: org.armedbear.lisp.Time$1.execute(Time.java:56) 86: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 87: org.armedbear.lisp.Lisp.evalCall(Lisp.java:550) 88: org.armedbear.lisp.Lisp.eval(Lisp.java:515) 89: org.armedbear.lisp.Lisp.eval(Lisp.java:508) 90: org.armedbear.lisp.Load.loadStream(Load.java:570) 91: org.armedbear.lisp.Load.loadFileFromStream(Load.java:526) 92: org.armedbear.lisp.Load.load(Load.java:201) 93: org.armedbear.lisp.Load.load(Load.java:686) 94: org.armedbear.lisp.Load$_load.execute(Load.java:636) 95: org.armedbear.lisp.Symbol.execute(Symbol.java:837) 96: org.armedbear.lisp.LispThread.execute(LispThread.java:701) 97: org.armedbear.lisp.load_1.execute(load.lisp:33) 98: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:101) 99: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 100: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 101: org.armedbear.lisp.ASDF_TMP_package_5.execute(package.lisp:22) 102: org.armedbear.lisp.Time$1.execute(Time.java:56) 103: org.armedbear.lisp.Symbol.execute(Symbol.java:802) 104: org.armedbear.lisp.LispThread.execute(LispThread.java:649) 105: org.armedbear.lisp.ASDF_TMP_package_1.execute(package.lisp:22) 106: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:112) 107: org.armedbear.lisp.Symbol.execute(Symbol.java:813) 108: org.armedbear.lisp.LispThread.execute(LispThread.java:666) 109: org.armedbear.lisp.Primitives$pf_funcall.execute(Primitives.java:2710) 110: (DELETE-PACKAGE "LOOP.16.PACKAGE") 111: (#<FUNCTION {233F70E0}>) 112: (JRUN-EXCEPTION-PROTECTED #<FUNCTION {233F70E0}>) 113: (#<FUNCTION (LAMBDA ()) {1A0B9434}>) 114: (#<FUNCTION {6E2EEF47}>) 115: (JRUN-EXCEPTION-PROTECTED #<FUNCTION {6E2EEF47}>) 116: (#<FUNCTION {4B5F56D4}>) 117: (JRUN-EXCEPTION-PROTECTED #<FUNCTION {4B5F56D4}>) 118: (REGRESSION-TEST::DO-ENTRY #S(REGRESSION-TEST::ENTRY :PEND NIL :NAME CL-TEST::LOOP.16.70 :PROPS NIL :FORM (LET NIL (IGNORE-ERRORS (DELETE- PACKAGE "LOOP.16.PACKAGE")) (LET (#) (LOOP #:FOR CL-TEST::X #:.. }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/194> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

[armedbear-ticket] [armedbear] #199: RESTAS fails when MOP:INITIAL-DISCRIMINATING-FUNCTION
by armedbear 22 May '12

22 May '12

#199: RESTAS fails when MOP:INITIAL-DISCRIMINATING-FUNCTION ------------------------------+--------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.0.2 Component: (A)MOP | Version: 1.0.1 Keywords: quicklisp restas | ------------------------------+--------------------------------------------- For the [https://github.com/archimag/restas RESTAS framework] loaded by the Feb 2012 Quicklisp the following MOP call fails when trying to run the 'examples/example-1.lisp' code: {{{ (MOP::INITIAL-DISCRIMINATING-FUNCTION #<STANDARD-GENERIC-FUNCTION SUBMODULE-ROUTES {59FAC3A2}> (#<RESTAS::PKG-SUBMODULE{23452A3E})) }}} I would like to either fix this for abcl-1.0.2 or get [http://trac.common- lisp.net/armedbear/ticket/198 abcl-1.1.0-dev working with Hunchentoot again], as I'm pretty sure this should be fixed easily in Rudi's code. {{{ Wrong number of arguments for #<FUNCTION (LAMBDA (ARGS NEXT-EMFUN)) {4B658B53}>. [Condition of type PROGRAM-ERROR] Restarts: 0: [RETRY] Retry SLIME interactive evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {17144A84}> #<PROGRAM-ERROR {35282BF2}> #<FUNCTION {17144A84}>) 1: (APPLY #<FUNCTION {17144A84}> (#<PROGRAM-ERROR {35282BF2}> #<FUNCTION {17144A84}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<PROGRAM-ERROR {35282BF2}> #<FUNCTION {17144A84}>) 3: (INVOKE-DEBUGGER #<PROGRAM-ERROR {35282BF2}>) 4: org.armedbear.lisp.Lisp.error(Lisp.java:381) 5: org.armedbear.lisp.Function.execute(Function.java:312) 6: org.armedbear.lisp.Primitive.execute(Primitive.java:113) 7: (#<STANDARD-GENERIC-FUNCTION SUBMODULE-ROUTES {59FAC3A2}> #<RESTAS ::PKG-SUBMODULE {605D3821}>) 8: (APPLY #<STANDARD-GENERIC-FUNCTION SUBMODULE-ROUTES {59FAC3A2}> (#<RESTAS::PKG-SUBMODULE {605D3821}>)) 9: (MOP::INITIAL-DISCRIMINATING-FUNCTION #<STANDARD-GENERIC-FUNCTION SUBMODULE-ROUTES {59FAC3A2}> (#<RESTAS::PKG-SUBMODULE {605D3821}>)) 10: (RESTAS:SUBMODULE-ROUTES #<RESTAS::PKG-SUBMODULE {605D3821}>) 11: (RESTAS:CONNECT-SUBMODULE #<RESTAS::PKG-SUBMODULE {605D3821}> #<ROUTES:MAPPER {8102FF4}>) 12: (RESTAS::ADD-TOPLEVEL-SUBMODULE #<RESTAS::PKG-SUBMODULE {605D3821}> NIL 8080) 13: (RESTAS:START #:RESTAS.EXAMPLE-1 :PORT 8080) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/199> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 19

[armedbear-ticket] [armedbear] #209: ASDF uses compile time rather than load time values for computing fasl location
by armedbear 18 May '12

18 May '12

#209: ASDF uses compile time rather than load time values for computing fasl location ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: ASDF | Version: 1.0.1 Keywords: | ----------------------+----------------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2307 Paul Nathan reports] {{{ I installed Armed Bear Common Lisp 1.0.1-svn-13750-13751 in order to run it on my OSX 10.6 (Snow Leopard) 64-bit system (Darwin 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 x86_64), for the purpose of executing cl-test-grid. However, I observed that the fasls were being stored in ~/.cache/common- lisp/abcl-1.0.1-svn-13750-13751-fasl38-solaris-x86 }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/209> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #205: JSS logic for resolving methods a little wonky (could use better diagnostics on why resolution has failed)
by armedbear 16 May '12

16 May '12

#205: JSS logic for resolving methods a little wonky (could use better diagnostics on why resolution has failed) -----------------------------------+---------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: libraries | Version: 1.0.1 Keywords: jss method-resolution | -----------------------------------+---------------------------------------- [http://thread.gmane.org/gmane.lisp.armedbear.devel/2252 Jonathan P. Bona is working with Alan Ruttenberg] to port LSW from JSS 1 to JSS 3: {{{ I'm working with Alan Ruttenberg to port LSW from the old version of JSS to the JSS that is now part of abcl-contrib. We've run into the following bug when using with-constant-signature: ; these first two work fine: (#"substring" "some string" 2 4) ; "me" (#"substring" "some string" 2) ; "me string" ; and so does this (with-constant-signature ((substring "substring")) (substring "some string" 2 4)) ; "me" ; but this breaks: (with-constant-signature ((substring "substring")) (substring "some string" 2)) ; Wrong number of arguments for public java.lang.String java.lang.String.substring(int,int): expected 2, got 1 ; [Condition of type PROGRAM-ERROR] A problem seems to be in jss::invoke-find-method, which is finding the two argument version of java.lang.String.substring no matter how many arguments its given: (jss::invoke-find-method "substring" "this is a string" '(1)) ; should return the java.lang.String.substring method with one int arg ; #<method public java.lang.String java.lang.String.substring(int,int)> (jss::invoke-find-method "substring" "this is a string" '(1 2) ) ; #<method public java.lang.String java.lang.String.substring(int,int)> (jss::invoke-find-method "substring" "this is a string" '(1 2 3 4 5 6 7 8) ) ; should be an error ; #<method public java.lang.String java.lang.String.substring(int,int) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/205> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #74: slow compilation test
by armedbear 06 May '12

06 May '12

#74: slow compilation test -------------------------+-------------------------------------------------- Reporter: trittweiler | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: | -------------------------+-------------------------------------------------- (eval-when (:compile-toplevel :load-toplevel :execute) (defclass foo () ())) (defun quux (x) (case x (#. (find-class 'foo) :foo) (t :quux))) (flet ((test (x) (format t "~&(QUUX ~S) => ~S~%" x (quux x)))) (test 42) (test (find-class 'foo))) COMPILE-FILE'ing that takes over a second. No real life case, of course, still you may be interested. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/74> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 4

[armedbear-ticket] [armedbear] #196: STABLE-SORT is only stable for lists
by armedbear 06 May '12

06 May '12

#196: STABLE-SORT is only stable for lists ------------------------------+--------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: interpreter | Version: 1.0.1 Keywords: ansi-conformance | ------------------------------+--------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2204 Jorge Tavares reports on armedbear-devel@]: {{{ Recently I started to investigate the different CL sort implementations and found that stable-sort in ABCL does not execute as required. The problem is that stable-sort is only stable for lists and not for all type of sequences (i.e., elements considered equal by the predicate should stay in their original order). A very simple test shows this error: idesk:~ jast$ abcl Armed Bear Common Lisp 1.0.1 Java 1.6.0_29 Apple Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.399 seconds. Startup completed in 1.069 seconds. Loading /Users/jast/.abclrc completed in 4.8 seconds. Type ":help" for a list of available commands. CL-USER(1): (defparameter *stuff* #((1 0.31648433) (0 0.2704757) (0 0.48931926) (1 0.9958766) (0 0.49251676))) *STUFF* CL-USER(2): (setf *stuff* (stable-sort *stuff* #'< :key #'first)) #((0 0.49251676) (0 0.2704757) (0 0.48931926) (1 0.31648433) (1 0.9958766)) The above test is short and simple to understand: *stuff* contains an array where each element is a pair. The first element of a pair is the key and the second the data. With this in mind, the expected result should have been: #((0 0.2704757) (0 0.48931926) (0 0.49251676) (1 0.31648433) (1 0.9958766)). The same error happens with larger arrays and other types of data. I also tested it in SBCL, CCL, ECL and CLisp and for these implementations the results are the expected. Only ABCL differs form the major open source implementations (I didn't test in ACL or LW). The reason for this bug is actually quite simple. In sort.lisp, in the definition of stable-sort, seq-dispatch calls for the non-list sequences the quicksort algorithm, which is not stable. For lists it calls merge sort (which is stable) and the problem does not arise. As a quick fix, I send in attach a patch that uses in stable-sort merge sort for all sequences. This is done by coercing the sequence to list, calling merge sort and coercing it back to the original sequence type. However, as a long term improvement, the best solution would be to implement a merge sort for non-list sequences. }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/196> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 6