#48: SLIME CVS HEAD as of 2008-12-30 broken
-------------------------------------+--------------------------------------
Reporter: mevenson | Owner: mevenson
Type: defect | Status: new
Priority: major | Milestone: 0.13
Component: other | Version: 1.0
Keywords: slime emacs application |
-------------------------------------+--------------------------------------
Symptom is the failed listening to SlimeInputStream that doesn't detect a
pipe close, therefore never closes, so further enviornment bindings are
incorrect.
*inferior-lisp* buffers needs to evaluate a form before SLIME works
properly.
Something messed up in the Stream ._finishOuput() calls??
--
Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/48>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#77: FASLs use wrong encoding: system default
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: ehuelsmann
Type: defect | Status: new
Priority: critical | Milestone: 0.19
Component: compiler | Version:
Keywords: |
------------------------+---------------------------------------------------
Because FASLs are using the system default encoding, we can't be sure they
can hold all characters which Java (and thus Lisp) can handle.
Additionally, reading back FASLs on systems which have a different default
encoding might break.
Solution: use UTF-8 as the encoding for FASLs.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/77>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#2: Human readable printing of errors and conditions
--------------------------+-------------------------------------------------
Reporter: ehuelsmann | Owner: somebody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: other | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Comment(by ehuelsmann):
The source of this behaviour is the fact that in some cases the 'format-
control slot in the built-in condition doesn't get set.
When that happens, the print-object code in print-object.lisp doesn't get
triggered to print the nice message, but rather passes control to the
standard object printing routine (which prints the ugly output above).
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/2#comment:2>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#75: Character \U0080 causes infinite loop
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone:
Component: CLOS | Version:
Keywords: |
------------------------+---------------------------------------------------
The following code causes an infinite loop on systems which do not support
character \U0080 in their default output character set:
(defparameter single-character-symbols
'#.(let ((a (make-array 129)))
(dotimes (i 129)
(setf (svref a i) (make-string 1 :initial-element (code-char i))))
a))
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/75>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#72: Faster startup times
-------------------------+--------------------------------------------------
Reporter: ehuelsmann | Owner: somebody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: other | Version:
Keywords: performance |
-------------------------+--------------------------------------------------
Analysis learned that 40% of the execution time spent loading ABCL was
spent finding constructors in the Java reflection code.
The idea of this issue is to spread the cost of that 40% better over the
life time of the application by loading - but not resolving - function
classes until they're actually used, by introducing a proxy object of some
kind which holds only the byte array of class bytes.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/72>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#64: Caught (general) exceptions not rethrown everywhere
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone:
Component: other | Version:
Keywords: |
------------------------+---------------------------------------------------
The code base uses exceptions derived from ConditionThrowable (Go, Throw,
Return) to cause non-local transfers of control.
A special exception (ThreadDestroyed) has been derived to cause a jump to
the outer-most function in a LispThread. (This doesn't work in the main
thread, which isn't enclosed by a function in LispThread like those in
other threads.)
Some spots in our code seem to discard other exceptions than the ones
mentioned above. That's probably wrong in most cases.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/64>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#14: Support for a C-calling FFI for CFFI to build upon
--------------------------+-------------------------------------------------
Reporter: ehuelsmann | Owner: mevenson
Type: enhancement | Status: assigned
Priority: major | Milestone:
Component: other | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Changes (by mevenson):
* owner: somebody => mevenson
* status: new => assigned
Comment:
It looks like Luís Oliveira has [done the hard work][1]. Not sure what
the best way to support this in ABCL would be.
Maybe I should really start mirroring ASDF packages with ABCL-specific
patches until we get those patches merged upstream. But then I would like
to ABCL's support for ASDF up to current by implementing the long form of
CLOS's DEFINE-METHOD-COMBINATION. Chicken, meet egg.
[1]: http://common-lisp.net/~loliveira/patches/cffi-abcl.diff
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/14#comment:3>
armedbear <http://common-lisp.net/project/armedbear>
armedbear