February 2011 - armedbear-ticket - mailman3.common-lisp.net

[armedbear-ticket] [armedbear] #124: Failure to be an SBCL build host
by armedbear 25 Aug '11

25 Aug '11

#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

1 12

[armedbear-ticket] [armedbear] #116: Installing cl-unicode via quicklisp fails
by armedbear 19 Aug '11

19 Aug '11

#116: Installing cl-unicode via quicklisp fails ----------------------------------------+----------------------------------- Reporter: vvoutilainen | Owner: somebody Type: defect | Status: new Priority: major | Milestone: 0.25 Component: other | Version: Keywords: quicklisp world domination | ----------------------------------------+----------------------------------- Here's the printout and a reproduction recipe: ================================================== ; Loading "cl-unicode" ... ;;; Parsing Unicode file UnicodeData.txt ;;; Parsing Unicode file Scripts.txt ;;; Parsing Unicode file Blocks.txt ;;; Parsing Unicode file PropList.txt ;;; Parsing Unicode file DerivedAge.txt ;;; Parsing Unicode file BidiMirroring.txt ;;; Parsing Unicode file Jamo.txt ;;; Building hash tables ;;; Writing source file methods.lisp ;;; Writing source file hash-tables.lisp ;;; Writing source file lists.lisp ;;; Writing source file derived-properties ;;; Parsing Unicode file DerivedCoreProperties.txtjava.lang.ClassFormatError: Unknown constant tag 41 in class file org/armedbear/lisp/ASDF_TMP_hash_tables_2 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.lang.ClassLoader.defineClass(ClassLoader.java:480) at org.armedbear.lisp.FaslClassLoader.findClass(FaslClassLoader.java:95) at org.armedbear.lisp.FaslClassLoader.loadClass(FaslClassLoader.java:77) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2406) at java.lang.Class.getConstructor0(Class.java:2716) at java.lang.Class.newInstance0(Class.java:343) at java.lang.Class.newInstance(Class.java:325) ... ================================================== Reproduce: 1. Install Quicklisp 2. (ql:quickload :cl-unicode) -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/116> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 7

[armedbear-ticket] [armedbear] #96: Lambda list &rest compilation error
by armedbear 06 Aug '11

06 Aug '11

#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

1 3

[armedbear-ticket] [armedbear] #122: writeToString infrastructure doesn't support *PRINT-CIRCLE*
by armedbear 06 Aug '11

06 Aug '11

#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

1 2

[armedbear-ticket] [armedbear] #131: LISP-IMPLEMENTATION-VERSION with svn information breaks SLIME.
by armedbear 05 Aug '11

05 Aug '11

#131: LISP-IMPLEMENTATION-VERSION with svn information breaks SLIME. ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: | ----------------------+----------------------------------------------------- Reported by ehu via #abcl. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/131> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #56: Eliminate use of temporary files in COMPILE and COMPILE-FILE
by armedbear 02 Aug '11

02 Aug '11

#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

1 7

[armedbear-ticket] [armedbear] #69: Gray stream compatibility
by armedbear 28 Apr '11

28 Apr '11

#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

1 6

[armedbear-ticket] [armedbear] #129: ql:JAN2011:montezuma produces a stack inconsistency
by armedbear 04 Mar '11

04 Mar '11

#129: ql:JAN2011:montezuma produces a stack inconsistency ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 0.25 Component: compiler | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- To reproduce: {{{ CL-USER> (load "http://beta.quicklisp.org/quicklisp.lisp") ... CL-USER> (quicklisp-quickstart:install) ... CL-USER> (ql:quickload "montezuma") }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/129> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #128: ABCL command line processing should terminate with '--'
by armedbear 20 Feb '11

20 Feb '11

#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

1 3

[armedbear-ticket] [armedbear] #123: REGISTER-JAVA-EXCEPTION failing
by armedbear 14 Feb '11

14 Feb '11

#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

1 4