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

[armedbear-ticket] [armedbear] #113: DEFSTRUCT redefinition can crash ABCL on MAKE-FOO
by armedbear 19 Aug '12

19 Aug '12

#113: DEFSTRUCT redefinition can crash ABCL on MAKE-FOO ---------------------+------------------------------------------------------ Reporter: mseddon | Owner: nobody Type: defect | Status: new Priority: minor | Milestone: Component: java | Version: Keywords: | ---------------------+------------------------------------------------------ CL-USER(1): (defstruct foo x y) FOO CL-USER(2): (defstruct foo x y z) FOO CL-USER(3): (make-foo :x 1 :y 2 :z 3) ABCL Debug.assertTrue() assertion failed! java.lang.Error: ABCL Debug.assertTrue() assertion failed! at org.armedbear.lisp.Debug.assertTrue(Debug.java:46) at org.armedbear.lisp.StructureObject.writeToString(StructureObject.java :483) Multiple DEFSTRUCTs do not change the underlying structure class, but seem to cause StructureObject to assert if the new (almost ignored) definition had a different number of slots than the old. For example, while the above example crashes out ABCL, the following example does not: CL-USER(1): (defstruct foo a b c) FOO CL-USER(2): (defstruct foo x y z) FOO CL-USER(3): (make-foo :x 1 :y 2 :z 3) #S(FOO :A 1 :B 2 :C 3) -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/113> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 10

[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] #214: Stack overflow when compiler macro with fallback is triggered
by armedbear 12 Aug '12

12 Aug '12

#214: Stack overflow when compiler macro with fallback is triggered ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: compiler | Version: 1.0.1 Keywords: | ----------------------+----------------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2352 James Lawerence reports] {{{ (eval-when (:compile-toplevel :load-toplevel :execute) (defun foo () 99) (define-compiler-macro foo () `(locally (declare (notinline foo)) (foo)))) (defun call-foo () (foo)) }}} Of course, the use case is a compiler macro that says, "OK, let's optimize! ... Never mind, I don't want to optimize that." {{{ Armed Bear Common Lisp 1.0.1-svn-13750-13751 Java 1.7.0_04 Oracle Corporation [...] ; (DEFUN FOO ...) ; (DEFINE-COMPILER-MACRO FOO ...) ; (DEFUN CALL-FOO ...) java.lang.StackOverflowError at org.armedbear.lisp.StructureObject$pf_make_structure.execute(StructureObject.java:671) at org.armedbear.lisp.Symbol.execute(Symbol.java:865) at org.armedbear.lisp.LispThread.execute(LispThread.java:760) at org.armedbear.lisp.jvm_714.execute(jvm.lisp:567) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/214> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[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