November 2008 - armedbear-ticket - mailman3.common-lisp.net

[armedbear-ticket] [armedbear] #28: Adjustable array not adjustable
by armedbear 16 Jan '09

16 Jan '09

#28: Adjustable array not adjustable ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | ------------------------+--------------------------------------------------- Alex Mizrahi writes: if multidimensional array is created as non-adjustable, it can be adjusted (new array is created). if multidimensional array is created as adjustable, it cannot be adjusted: adjust-array signals "ADJUST-ARRAY: unsupported case." error. for one dimensional array (vector) all is well. while i understand that this is probably just feature missing, this appears to be weird: if you want array to become adjustable, it becomes not. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/28> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #27: Support for reading files in other than ISO-8859-1 encodings (UTF-8)
by armedbear 12 Jan '09

12 Jan '09

#27: Support for reading files in other than ISO-8859-1 encodings (UTF-8) -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- Both Alex Mizrahi and Hideo Yokohama write: It would be nice if ABCL would support any other encodings than ISO-8859-1 (latin1); especially since Java *does* support it. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/27> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

[armedbear-ticket] [armedbear] #22: keyword parameters by same name as global variable
by armedbear 08 Dec '08

08 Dec '08

#22: keyword parameters by same name as global variable ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | ------------------------+--------------------------------------------------- Don Cohen writes that the code below is problematic. Especially because of the DEFVAR form. ==== /tmp/build1 (in-package :cl-user) (defpackage "AP5" (:use "CL") (:nicknames "ap5")) (in-package :ap5) (load "/tmp/compile.lsp" :print t) (setf source-default-path "/backup/shuttle/home/don/ap5-2006/foo.lsp" bin-default-path "/tmp/build-ap5/foo.fas") (ensure-directories-exist bin-default-path) (COMPILE-AP5 :recompile t) ;;(compile-ap5 :ask t) ==== /tmp/compile.lsp (in-package "AP5") (defvar info nil) (defvar ask nil) (defvar recompile nil) (defvar nevercompile nil) (defvar *changed* nil) (defvar startfile nil) (defvar stopfile t) (defvar *start-time* 0) (defun compile-ap5 (&key recompile nevercompile info ask (break-at-end #+symbolics t) startfile (stopfile t) &aux *changed* (*start-time* (get-universal-time)) #+(or symbolics ti) (global:inhibit-fdefine- warnings t)) ; (compile-load "sys-depend") (declare (special generator-cost-record record-expensive-and-costs)) ) -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/22> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #23: RETURN handled differently in interpreted and compiled code
by armedbear 24 Nov '08

24 Nov '08

#23: RETURN handled differently in interpreted and compiled code ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | ------------------------+--------------------------------------------------- Robert Dodier writes: See below for foobar.lisp. Interpreted: (foobar) => HELLO 1 NIL Compiled: (foobar) => HELLO 1 HELLO 2 T I'm no expert on the CL spec so I don't know which is correct. But I think Maxima expects the behavior shown by interpreted code here. Thanks for your attention to this. Robert Dodier PS. $ cat foobar.lisp (defun blurf () nil) (defun foobar () (prog (x y z) (declare (ignore x y z)) ((lambda (a b) (declare (ignore a b)) (format t "HELLO 1~%") (cond ((not (blurf)) (return nil)))) nil nil) (format t "HELLO 2~%") (return t))) -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/23> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

[armedbear-ticket] [armedbear] #31: Create example code for various use cases of ABCL
by armedbear 08 Nov '08

08 Nov '08

#31: Create example code for various use cases of ABCL --------------------------+------------------------------------------------- Reporter: vvoutilainen | Owner: vvoutilainen Type: task | Status: new Priority: major | Milestone: 0.12 Component: component1 | Version: Keywords: | --------------------------+------------------------------------------------- It would be useful to have example code so that we can point new people to actual, working examples. The previous discussion on the mailing list have been vague at best, and sometimes even gave incorrect advice. The following cases should be shown in the examples: 1) calling lisp code from java code 2) calling java code from lisp code 3) implementing a java interface in lisp code -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/31> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

Re: [armedbear-ticket] [armedbear] #7: SLIME support (delivered with ABCL) needs updating
by armedbear 02 Nov '08

02 Nov '08

#7: SLIME support (delivered with ABCL) needs updating -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: closed Priority: minor | Milestone: Component: component1 | Version: Resolution: fixed | Keywords: -------------------------+-------------------------------------------------- Changes (by ehuelsmann): * status: assigned => closed * resolution: => fixed Comment: All slime artifacts have been removed. remove-slime-build.patch committed in r11376. Closing this issue. (We don't need to deliver Slime with ABCL; Slime CVS changes too often to keep up. Users should download their own.) -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/7#comment:10> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

Re: [armedbear-ticket] [armedbear] #7: SLIME support (delivered with ABCL) needs updating
by armedbear 02 Nov '08

02 Nov '08

#7: SLIME support (delivered with ABCL) needs updating -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: assigned Priority: minor | Milestone: Component: component1 | Version: Resolution: | Keywords: -------------------------+-------------------------------------------------- Comment(by mevenson): Replying to [comment:7 ehuelsmann]: > But: > > (require 'asdf) > (require 'gray-streams) > (asdf:oos 'asdf:load-op :swank) > > breaks the asdf operation. > > See ticket #20. The patch [attached to ticket #20][1] allows this operation to succeed. [1]: http://trac.common-lisp.net/armedbear/attachment/ticket/20/pprint- gray-streams.lisp -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/7#comment:9> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

Re: [armedbear-ticket] [armedbear] #7: SLIME support (delivered with ABCL) needs updating
by armedbear 02 Nov '08

02 Nov '08

#7: SLIME support (delivered with ABCL) needs updating -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: assigned Priority: minor | Milestone: Component: component1 | Version: Resolution: | Keywords: -------------------------+-------------------------------------------------- Comment(by mevenson): The build system for ABCL should be further "tightened" with the 'remove- old-slime.patch', removing the references to the removed files in 'build.xml' as well as 'compile-system.lisp'. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/7#comment:8> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

Re: [armedbear-ticket] [armedbear] #7: SLIME support (delivered with ABCL) needs updating
by armedbear 02 Nov '08

02 Nov '08

#7: SLIME support (delivered with ABCL) needs updating -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: assigned Priority: minor | Milestone: Component: component1 | Version: Resolution: | Keywords: -------------------------+-------------------------------------------------- Comment(by ehuelsmann): But: (require 'asdf) (require 'gray-streams) (asdf:oos 'asdf:load-op :swank) breaks the asdf operation. See ticket #20. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/7#comment:7> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

Re: [armedbear-ticket] [armedbear] #7: SLIME support (delivered with ABCL) needs updating
by armedbear 02 Nov '08

02 Nov '08

#7: SLIME support (delivered with ABCL) needs updating -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: assigned Priority: minor | Milestone: Component: component1 | Version: Resolution: | Keywords: -------------------------+-------------------------------------------------- Comment(by ehuelsmann): BTW, swank-gray compiles without warnings on the latest of trunk (r11375). -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/7#comment:6> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0