#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
#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
#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
#172: DOCUMENTATION does not work for generic functions
-------------------------+--------------------------------------------------
Reporter: mevenson | Owner: ehuelsmann
Type: defect | Status: new
Priority: minor | Milestone: 0.28
Component: interpreter | Version: 0.27
Keywords: |
-------------------------+--------------------------------------------------
DOCUMENTATION does not seem to be able to retrieve the docstring for
generic functions:
{{{
(defgeneric foo nil (:documentation "Ipso facto"))
#<STANDARD-GENERIC-FUNCTION FOO {6901DFA5}>
CL-USER> (documentation 'foo 'function)
NIL
}}}
If one inspects the generic function in SLIME, one sees that the
documentation slot does have a value, so this is a problem in
DOCUMENTATION.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/172>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#30: Lisp debugger, for both compiled and interpreted code
----------------------------+-----------------------------------------------
Reporter: vvoutilainen | Owner: somebody
Type: enhancement | Status: new
Priority: major | Milestone: unscheduled
Component: component1 | Version:
Keywords: debug debugger |
----------------------------+-----------------------------------------------
ABCL code can be debugged with normal java debuggers, but it
is somewhat painful for the portions implemented in lisp(1). So we need a
lisp debugger.
(1) It's possible, although a bit tedious, to step through
eval calls in a java debugger by examining the cars and
cdrs of eval parameters when stepping the code.
--
Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/30>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#127: SLIME fails to EXTENSION:QUIT
-------------------------+--------------------------------------------------
Reporter: mevenson | Owner: ehuelsmann
Type: defect | Status: new
Priority: major | Milestone: unscheduled
Component: interpreter | Version: 0.24
Keywords: slime |
-------------------------+--------------------------------------------------
Alan Ruttenberg reports that "(QUIT) in SLIME doesn't"
{{{
CL-USER> (quit)
; Evaluation aborted on NIL.
}}}
The REPL used by SLIME is failing to catch and properly interpret the new
ProcessingTerminated exception thrown by QUIT.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/127>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#170: Make COMPILE-FILE a multi-pass operation
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: ehuelsmann
Type: defect | Status: new
Priority: major | Milestone:
Component: compiler | Version:
Keywords: |
------------------------+---------------------------------------------------
The single-pass implementation of COMPILE-FILE has several drawbacks:
1. Only backward referenced function calls can be inlined (since forward
referenced functions are unknown at the time of compilation)
1. It's much harder to build an fasl-literal-object table with objects
being referenced multiple times in the fasl; we need this item for
compliance with
[http://www.lispworks.com/documentation/HyperSpec/Body/03_bdd.htm section
3.2.4.4 of the CLHS]
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/170>
armedbear <http://common-lisp.net/project/armedbear>
armedbear