December 2010 - armedbear-ticket - mailman3.common-lisp.net

[armedbear-ticket] [armedbear] #66: Support for DEFINE-METHOD-COMBINATION (long form)
by armedbear 11 Sep '11

11 Sep '11

#66: Support for DEFINE-METHOD-COMBINATION (long form) ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: | ------------------------+--------------------------------------------------- ABCL does not support D-M-C. It should. Patches welcome. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/66> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 15

[armedbear-ticket] [armedbear] #115: Generate specific classes for compiled Go/Return
by armedbear 07 Sep '11

07 Sep '11

#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

1 1

[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] #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] #67: initarg checking performance
by armedbear 13 Feb '11

13 Feb '11

#67: initarg checking performance -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: performance | -------------------------+-------------------------------------------------- Our initarg checking strictness has improved (used to be non-existent), but we've seen a rather large performance hit, amongst other things upon object instantiation (make-instance). Functions involved (?): ALLOCATE-INSTANCE INITIALIZE-INSTANCE REINITIALIZE-INSTANCE SHARED-INITIALIZE UPDATE-INSTANCE-FOR-DIFFERENT-CLASS UPDATE-INSTANCE-FOR-REDEFINED-CLASS -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/67> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #83: problem with error reporting on undefined class during make instance
by armedbear 13 Feb '11

13 Feb '11

#83: problem with error reporting on undefined class during make instance ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: | ------------------------+--------------------------------------------------- CL-USER(25): (defclass c (d) ((q :initarg :q))) #<STANDARD-CLASS C {B5BEE0}> CL-USER(26): (make-instance 'c :q t) Debugger invoked on condition of type PROGRAM-ERROR: Invalid initarg :Q. The error should say instead something about d not being defined. This in build of a freshly updated trunk abcl -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/83> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #18: Incorporate 'invoke.lisp' dynamic classpath ability
by armedbear 23 Jan '11

23 Jan '11

#18: Incorporate 'invoke.lisp' dynamic classpath ability -------------------------+-------------------------------------------------- Reporter: mevenson | Owner: somebody Type: enhancement | Status: new Priority: minor | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- Alan Ruttenberg's [invoke.lisp][1] has the ability to easily add additional Java JARs at runtime by using the [beanshell classloader][2]. With a few additions to the ASDF system, this allows one to easily specify "wrappings" of Java components which load JARs or find classfiles on the filesystem. The code in the Beanshell classmanager could be added to the ABCL src tree fairly easily to facilitate this behavior. [1]: http://svn.mumble.net:8080/svn/lsw/trunk/jss/invoke.lisp [2]: http://www.beanshell.org/home.html -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/18> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #109: When TPL::REPL is unavailable, the debugger kills the entire application
by armedbear 23 Jan '11

23 Jan '11

#109: When TPL::REPL is unavailable, the debugger kills the entire application ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: libraries | Version: Keywords: | ------------------------+--------------------------------------------------- Ole Myren Rohne reports: "" I'm playing with AbclScriptEngine (with Electric VLSI) and found a tiny problem with config.lisp: EXT:MAKE-THREAD should be THREADS:MAKE-THREAD. "" which is already solved, but continues: Unfortunately the problem was unnecessary hard to debug because in the absence of TPL::REPL the debugger ends up quitting the entire application. I'm wondering if in that case it would be more useful to throw a Java error, eg like SYS::%DEBUGGER-HOOK-FUNCTION? That's what this ticket is about. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/109> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3