armedbear-ticket February 2011

armedbear-ticket@common-lisp.net

1 participants
33 discussions

[armedbear-ticket] [armedbear] #34: adjust generated '*.cls' filenames
by armedbear 14 Jul '12

14 Jul '12

#34: adjust generated '*.cls' filenames ------------------------+--------------------------------------------------- Reporter: mevenson | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | ------------------------+--------------------------------------------------- dmiles: it be nice to eventually name the coerce-666.cls coerce_666.cls as the same name of the way classpaths think about them (they'd continue to work).. one argument agaist is our autoloader at least gets a better whack at finding them in the right context apart from classloader -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/34> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #74: slow compilation test
by armedbear 06 May '12

06 May '12

#74: slow compilation test -------------------------+-------------------------------------------------- Reporter: trittweiler | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: | -------------------------+-------------------------------------------------- (eval-when (:compile-toplevel :load-toplevel :execute) (defclass foo () ())) (defun quux (x) (case x (#. (find-class 'foo) :foo) (t :quux))) (flet ((test (x) (format t "~&(QUUX ~S) => ~S~%" x (quux x)))) (test 42) (test (find-class 'foo))) COMPILE-FILE'ing that takes over a second. No real life case, of course, still you may be interested. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/74> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 4

[armedbear-ticket] [armedbear] #30: Lisp debugger, for both compiled and interpreted code
by armedbear 18 Nov '11

18 Nov '11

#30: Lisp debugger, for both compiled and interpreted code ----------------------------+----------------------------------------------- Reporter: vvoutilainen | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: unscheduled Component: component1 | Version: Keywords: debug debugger | ----------------------------+----------------------------------------------- ABCL code can be debugged with normal java debuggers, but it is somewhat painful for the portions implemented in lisp(1). So we need a lisp debugger. (1) It's possible, although a bit tedious, to step through eval calls in a java debugger by examining the cars and cdrs of eval parameters when stepping the code. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/30> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 4

[armedbear-ticket] [armedbear] #127: SLIME fails to EXTENSION:QUIT
by armedbear 18 Nov '11

18 Nov '11

#127: SLIME fails to EXTENSION:QUIT -------------------------+-------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: unscheduled Component: interpreter | Version: 0.24 Keywords: slime | -------------------------+-------------------------------------------------- Alan Ruttenberg reports that "(QUIT) in SLIME doesn't" {{{ CL-USER> (quit) ; Evaluation aborted on NIL. }}} The REPL used by SLIME is failing to catch and properly interpret the new ProcessingTerminated exception thrown by QUIT. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/127> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 6

[armedbear-ticket] [armedbear] #84: jcall and t/nil boolean arguments
by armedbear 11 Sep '11

11 Sep '11

#84: jcall and t/nil boolean arguments ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: java | Version: Keywords: | ------------------------+--------------------------------------------------- Can it be made so that within jcall, t or nil is understood as a java boolean argument? -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/84> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[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] #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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-ticket February 2011