#115: Generate specific classes for compiled Go/Return
-------------------------+--------------------------------------------------
Reporter: ehuelsmann | Owner: ehuelsmann
Type: enhancement | Status: new
Priority: major | Milestone:
Component: compiler | Version:
Keywords: |
-------------------------+--------------------------------------------------
By using specific classes for Go/Return, we could make our exception
handling more targetted; there would be no sifting through all the
unwinding levels for the right level (unpacking the 'return-tag' or 'go-
tag').
Instead, the jump would hit all the finally clauses without further
checking; straight through to the right handler.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/115>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#121: p2-test-* infrastructure should use COMPILE-TEST-FORM
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: ehuelsmann
Type: defect | Status: new
Priority: major | Milestone:
Component: compiler | Version:
Keywords: |
------------------------+---------------------------------------------------
Where it sometimes uses COMPILE-FORM and tests for NIL.
Another idea is to use FAIL/SUCCESS labels as argument to the compile-
test-function, which may result in more more efficient code. For example,
in that case, a NOT compilation only requires reversing the labels.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/121>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#134: Better support for packaging systems in jar files
--------------------------------+-------------------------------------------
Reporter: mevenson | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone: 0.26
Component: java | Version:
Keywords: asdf jar packaging |
--------------------------------+-------------------------------------------
Meta ticket for collecting requirements for packaging systems in jar
files. Currently support exists for loading ASDF2 systems as source
packaged in a jar (see ABCL's contrib via the Ant target 'abcl.contrib'),
but additional support is often requested.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/134>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#135: ql:FEB2011:bordeaux-threads BORDEAUX-THREADS does not work
------------------------------------------------+---------------------------
Reporter: mevenson | Owner: mevenson
Type: defect | Status: new
Priority: major | Milestone: 0.25
Component: libraries | Version: 0.24
Keywords: bordeaux-threads quicklisp threads |
------------------------------------------------+---------------------------
[http://common-lisp.net/project/bordeaux-threads/ bordeaux-threads] fails
with ABCL due to a number of reasons for which I am in progress of working
through patches. This issue will track the status of these patches
against the progress of those patches against both [http://common-lisp.net/gitweb?p=projects/bordeaux-threads/bordeaux-threads.git;a=summary
BORDEAUX-THREADS in git] and [http://www.quicklisp.org/beta/ the version
distributed with QuickLisp] (the version of FEB2011 as of this writing).
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/135>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#124: Failure to be an SBCL build host
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: libraries | Version:
Keywords: |
------------------------+---------------------------------------------------
When building SBCL with ABCL, I'm getting the error
#<XP:XP-STRUCTURE ...> isn't of type STREAM
Failing to continue the SBCL build.
The issue here is that our pretty printer structure - which wraps a stream
- isn't itself a stream. Somehow, the pretty printer stream wrapper is
passed into ABCL internals expecting a STREAM, though.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/124>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#148: READTABLE-CASE :invert does not invert uninterned symbols
-----------------------------------+----------------------------------------
Reporter: mevenson | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: 0.26
Component: other | Version: 0.24
Keywords: readtable parenscript |
-----------------------------------+----------------------------------------
[http://article.gmane.org/gmane.lisp.armedbear.devel/1891 Ole Arendt
reports]:
This prevents loading a newer parenscript, which uses an
inverted readtable case via named-readtables:
{{{
Armed Bear Common Lisp 0.26.0-dev-svn-13273
Java 1.6.0_17 Sun Microsystems Inc.
Java HotSpot(TM) 64-Bit Server VM
Low-level initialization completed in 0.712 seconds.
Startup completed in 3.154 seconds.
Type ":help" for a list of available commands.
CL-USER(1): (setf (readtable-case *readtable*) :invert)
:invert
CL-USER(2): (string :cl)
"CL"
CL-USER(3): (string '#:cl)
"cl"
}}}
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/148>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#141: Fix the SETF expander to work with APPLY for arbitrary function
----------------------------+-----------------------------------------------
Reporter: mevenson | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: 0.26
Component: other | Version: 0.24
Keywords: setf quicklisp |
----------------------------+-----------------------------------------------
CL-CONTAINERS from Quicklist MAR2011 fails to compile because our SETF
expander for APPLY doesn't work for functions other than #'AREF, #'BIT,
and #'SBIT as can be seen [source:trunk/abcl/src/org/armedbear/lisp/late-
setf.lisp#L90 by the ERROR generated by late-setf.lisp].
The SETF expansion for APPLY should work with an arbitrary function.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/141>
armedbear <http://common-lisp.net/project/armedbear>
armedbear