#163: Local function bindings should shadow global environment
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: somebody
Type: defect | Status: new
Priority: critical | Milestone:
Component: CLOS | Version:
Keywords: |
------------------------+---------------------------------------------------
FLET and LABELS bound functions should shadow compiler macros, macros and
function bindings.
Currently, they only shadow global function definitions.
This is the problem that causes Parenscript 2.3 to fail compilation on
ABCL.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/163>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#161: Port NAMED-READTABLES
----------------------------------------------------+-----------------------
Reporter: mevenson | Owner: nobody
Type: defect | Status: new
Priority: minor | Milestone: unscheduled
Component: libraries | Version: 0.24
Keywords: quicklisp named-readtables parenscript |
----------------------------------------------------+-----------------------
As noted first in #148, newer versions of [http://common-lisp.net/project/parenscript/ Parenscript] fail to load because [http
://common-lisp.net/project/named-readtables/ named-readtables ] has not
been ported to ABCL.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/161>
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
#2: Human readable printing of errors and conditions
--------------------------+-------------------------------------------------
Reporter: ehuelsmann | Owner: somebody
Type: enhancement | Status: closed
Priority: major | Milestone: unscheduled
Component: other | Version:
Resolution: fixed | Keywords:
--------------------------+-------------------------------------------------
Changes (by ehuelsmann):
* status: new => closed
* resolution: => fixed
Comment:
Some of these have been fixed; no known others. Please reopen specific
bugs for specific cases.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/2#comment:5>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#96: Lambda list &rest compilation error
-----------------------------+----------------------------------------------
Reporter: mevenson | Owner: ehuelsmann
Type: defect | Status: new
Priority: minor | Milestone: unscheduled
Component: compiler | Version:
Keywords: compiler lambda |
-----------------------------+----------------------------------------------
The following lambda list
{{{
(defun hashmap-to-hashtable (&key (k #'identity) &rest rest)
(let ((foo)))
}}}
fails to compile with the error
{{{
&REST/&BODY must be followed by a variable.
}}}
Reported by Alan Ruttenberg
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/96>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#122: writeToString infrastructure doesn't support *PRINT-CIRCLE*
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: java | Version:
Keywords: |
------------------------+---------------------------------------------------
From a reaction of mine to a mail by Kevin Reid:
> I don't think it's a good idea to explicitly bind *print-circle* to
> nil in anything debugging-related, including error printing, because
> then it's a source of nontermination (silent until out of memory, if
> the output is going to a string) if user code is working with circular
> structure.
That's a good point. Rather, it may even be better to explicitly bind it
to T.
This remark made me realize that our Java side writeToString actually
doesn't support *PRINT-CIRCLE* which can be an issue when trying to debug
ABCL before it has loaded the ERROR and PRINT-OBJECT infrastructures.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/122>
armedbear <http://common-lisp.net/project/armedbear>
armedbear