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

[armedbear-ticket] [armedbear] #121: p2-test-* infrastructure should use COMPILE-TEST-FORM
by armedbear 07 Sep '11

07 Sep '11

#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

1 1

[armedbear-ticket] [armedbear] #120: p2-* and p2-test-* infrastructures overlap
by armedbear 07 Sep '11

07 Sep '11

#120: p2-* and p2-test-* infrastructures overlap ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: Component: compiler | Version: Keywords: | ------------------------+--------------------------------------------------- As an example, take p2-numeric-comparison and p2-test-numeric-comparison. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/120> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

[armedbear-ticket] [armedbear] #134: Better support for packaging systems in jar files
by armedbear 07 Sep '11

07 Sep '11

#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

1 4

[armedbear-ticket] [armedbear] #135: ql:FEB2011:bordeaux-threads BORDEAUX-THREADS does not work
by armedbear 07 Sep '11

07 Sep '11

#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

1 12

[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] #148: READTABLE-CASE :invert does not invert uninterned symbols
by armedbear 16 Aug '11

16 Aug '11

#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

1 1

[armedbear-ticket] [armedbear] #141: Fix the SETF expander to work with APPLY for arbitrary function
by armedbear 07 Aug '11

07 Aug '11

#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

1 1

[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