#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
#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
#56: Eliminate use of temporary files in COMPILE and COMPILE-FILE
-------------------------+--------------------------------------------------
Reporter: ehuelsmann | Owner: ehuelsmann
Type: enhancement | Status: new
Priority: major | Milestone:
Component: compiler | Version:
Keywords: |
-------------------------+--------------------------------------------------
The functions COMPILE and COMPILE-FILE use temporary files for the class
files generated by the compiler.
However, COMPILE directly loads them back into memory and deletes the temp
file, while COMPILE-FILE deletes the temp file after adding it to a ZIP
archive.
This ticket exists to indicate that infrastructure is required to better
manage where output goes to, abstracting from the temp files.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/56>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#69: Gray stream compatibility
---------------------------+------------------------------------------------
Reporter: ehuelsmann | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone:
Component: other | Version:
Keywords: compatibility |
---------------------------+------------------------------------------------
The last thing holding us back from being fully Gray stream compatible, is
that TYPEP should return T for any fundamental-stream derived instance
when tested against 'STREAM or (find-class 'STREAM).
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/69>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#128: ABCL command line processing should terminate with '--'
----------------------+-----------------------------------------------------
Reporter: mevenson | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone:
Component: CLOS | Version:
Keywords: |
----------------------+-----------------------------------------------------
Didier writes from
<http://www.didierverna.com/sciblog/index.php?post/2011/01/22/Towards-
ABCL-Standalone-Executables>:
{{{
Nope because ABCL will still eat options it recognizes as its own, even
after "--". In fact, I don't think ABCL has any notion of a double hyphen.
Besides, it doesn't help you build a complete application in a JAR file,
which was really my point.
}}}
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/128>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#123: REGISTER-JAVA-EXCEPTION failing
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: java | Version:
Keywords: |
------------------------+---------------------------------------------------
William writes:
Hi,
I am trying to register Java exceptions using REGISTER-JAVA-EXCEPTION but
it
does not seem to work for me as evidenced by the transcript below.
Is there anything that I may have missed?
Armed Bear Common Lisp 0.23.1
Java 1.6.0_20 Sun Microsystems Inc.
Java HotSpot(TM) 64-Bit Server VM
Low-level initialization completed in 0.354 seconds.
Startup completed in 1.579 seconds.
Type ":help" for a list of available commands.
CL-USER(1): (define-condition java-illegal-argument-error (java-exception)
())
JAVA-ILLEGAL-ARGUMENT-ERROR
CL-USER(2): (register-java-exception "java.lang.IllegalArgumentException"
'java-illegal-argument-error)
NIL
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/123>
armedbear <http://common-lisp.net/project/armedbear>
armedbear