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

[armedbear-ticket] Re: [armedbear] #337: PROBE-FILE for jar file entries accessed via http fails
by armedbear 05 Jan '14

05 Jan '14

#337: PROBE-FILE for jar file entries accessed via http fails --------------------------+----------------------------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.3.0 Component: interpreter | Version: 1.2.1-dev Resolution: | Keywords: jar-pathname abcl-test-lisp --------------------------+----------------------------------------- Old description: > Check: Is it just GOOG? > > {{{ > > (probe-file #P"jar:http://abcl-dynamic-install.googlecode.com/files/baz- > 20130403a.jar!/foo") > > }}} New description: {{{ (probe-file #P"jar:http://abcl.org/fasl/42/baz-20140105a- fasl-42.jar!/foo" }}} {{{ (probe-file #P"jar:http://abcl-dynamic-install.googlecode.com/files/baz- 20130403a.jar!/foo") }}} -- Comment (by mevenson): Not just GOOG: A newly created jar for remote FASL loads at #P"jar:http://abcl.org/fasl/42/baz-20140105a-fasl-42.jar!/" still fails the load. -- Ticket URL: <http://abcl.org/trac/ticket/337#comment:1> armedbear <http://abcl.org> armedbear

1 0

[armedbear-ticket] Re: [armedbear] #166: Stream wrapping streams conflict with pretty printer
by armedbear 29 Dec '13

29 Dec '13

#166: Stream wrapping streams conflict with pretty printer -------------------------+--------------------------------------------- Reporter: ehuelsmann | Owner: mevenson Type: defect | Status: assigned Priority: blocker | Milestone: 1.3.0 Component: libraries | Version: 1.1.0 Resolution: | Keywords: streams gray-streams needs-test -------------------------+--------------------------------------------- Changes (by mevenson): * owner: https://www.google.com/accounts/o8/id?id=AItOawkYnNNEAO_K40Gp0xROhyjOPgjvIs… => mevenson -- Ticket URL: <http://abcl.org/trac/ticket/166#comment:14> armedbear <http://abcl.org> armedbear

1 0

[armedbear-ticket] Re: [armedbear] #326: abcl cannot be compiled with Java5
by armedbear 29 Dec '13

29 Dec '13

#326: abcl cannot be compiled with Java5 -----------------------+----------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: accepted Priority: blocker | Milestone: 1.3.0 Component: java | Version: 1.3.0-dev Resolution: | Keywords: -----------------------+----------------------- Changes (by mevenson): * owner: nobody => mevenson * priority: minor => blocker * status: new => accepted -- Ticket URL: <http://abcl.org/trac/ticket/326#comment:1> armedbear <http://abcl.org> armedbear

1 0

[armedbear-ticket] Re: [armedbear] #334: Forms evaluated with `--eval` not in a "correct" interpreter environment
by armedbear 27 Dec '13

27 Dec '13

#334: Forms evaluated with `--eval` not in a "correct" interpreter environment -----------------------+----------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.3.0 Component: other | Version: 1.3.0-dev Resolution: | Keywords: asdf -----------------------+----------------------- Comment (by mevenson): The attached patch now correctly throws an semi-intelligble error on the Java side when a SHARPSIGN-DOT macro is passed as part of an '--eval' argument. This confirms that the problem seems to lie in the use of REQUIRE forms within '--eval' args. {{{ quoth:~/work/asdf$ abcl --noinit --eval '`#.(load (string `|test /script-support.lisp|) :verbose t :print t)' Armed Bear Common Lisp 1.3.0-dev Java 1.7.0_45 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.475 seconds. Startup completed in 2.41 seconds. ; Loading /Users/evenson/work/asdf/test/script-support.lisp ... #<PACKAGE ASDF-TEST> #<PACKAGE ASDF-TEST> NIL NIL *TRACE-SYMBOLS* *DEBUG-ASDF* *QUIT-WHEN-DONE* VERBOSE NIL NIL ASYM ACALL ASYMVAL ASYMVAL Failed to require LOOP because 'Illegal function object: (bqv).' Maximum error depth exceeded (11 nested errors) with 'Illegal function object: (bqv).'. CL-USER(1): }}} -- Ticket URL: <http://abcl.org/trac/ticket/334#comment:1> armedbear <http://abcl.org> armedbear

1 0

[armedbear-ticket] [armedbear] #335: CL:MAKE-PATHNAME doesn't support :back arguments
by armedbear 11 Dec '13

11 Dec '13

#335: CL:MAKE-PATHNAME doesn't support :back arguments -------------------------+------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.3.0 Component: interpreter | Version: 1.2.1 Keywords: asdf | -------------------------+------------------- Faré reports: See https://bugs.launchpad.net/asdf/+bug/1260011 http://www.lispworks.com/documentation/HyperSpec/Body/19_bbdc.htm [2] CL-USER(5): (make-pathname :directory '(:relative :back)) #<THREAD "interpreter" {2B3B7C28}>: Debugger invoked on condition of type FILE-ERROR Unsupported directory component BACK. Restarts: 0: ABORT Return to debug level 2. 1: ABORT Return to debug level 1. 2: TOP-LEVEL Return to top level. [3] CL-USER(6): (lisp-implementation-version) "1.2.1" "OpenJDK_64-Bit_Server_VM-Sun_Microsystems_Inc.-1.6.0_27-b27" "amd64-Linux-3.8.0-34-generic" [3] CL-USER(7): I suppose I can try to paper over it in ASDF. -- Ticket URL: <http://abcl.org/trac/ticket/335> armedbear <http://abcl.org> armedbear

1 0

[armedbear-ticket] [armedbear] #314: CL:FORMAT problems with ~F
by armedbear 03 Apr '13

03 Apr '13

#314: CL:FORMAT problems with ~F ------------------------------+--------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: 1.2.0 Component: interpreter | Version: 1.2.0-dev Keywords: ansi-conformance | ------------------------------+--------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2838 Carlos Ungil reports] {{{ > (format t "~,2f" 0.999) 1.0 ;; should be 1.00 }}} I think there is a problem here as well: {{{ > (format t "~5f" 0.00000001) .0000 ;; should print " 0.0" }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/314> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

[armedbear-ticket] [armedbear] #313: (COERCE 3 '(FLOAT * *)) fails
by armedbear 02 Apr '13

02 Apr '13

#313: (COERCE 3 '(FLOAT * *)) fails ----------------------------------------------------------------------------------------------+ Reporter: https://www.google.com/accounts/o8/id?id=aitoawmirmkhhsmhgi36otvnjvwc_guuvf… | Owner: somebody Type: defect | Status: new Priority: minor | Milestone: Component: other | Version: 1.2.0-dev Keywords: coerce, float | ----------------------------------------------------------------------------------------------+ (COERCE 3 '(FLOAT * *)) fails with "3 cannot be converted to type (FLOAT * *)". Similar expressions with other float types, e.g. with DOUBLE-FLOAT, SINGLE-FLOAT, LONG-FLOAT, SHORT-FLOAT, all fail. Similar expressions with explicit bounds, e.g. (COERCE 3 '(FLOAT -10f0 10f0)) and other float types, all fail. ABCL version = Armed Bear Common Lisp 1.2.0-dev (built from svn r14454). Found this while running Maxima test suite. ev(zeta(3 + %i), numer) triggers this error. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/313> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

[armedbear-ticket] [armedbear] #166: Stream wrapping streams conflict with pretty printer
by armedbear 31 Mar '13

31 Mar '13

#166: Stream wrapping streams conflict with pretty printer ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: libraries | Version: Keywords: | ------------------------+--------------------------------------------------- The stream wrapping streams * BroadcastStream * CaseFrobStream * EchoStream * TwoWayStream * ConcatenatedStream can't wrap Gray streams and the XP-STRUCTURE pretty printer structure. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/166> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 11

[armedbear-ticket] [armedbear] #311: UIOP fails to load
by armedbear 27 Mar '13

27 Mar '13

#311: UIOP fails to load -----------------------+---------------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: 1.2.0 Component: libraries | Version: 1.2.0-dev Keywords: | -----------------------+---------------------------------------------------- Anton noticed with the cl-test-grid results that UIOP fails to load on abcl-1.2.0-dev which I bisected to the following changeset {{{ The first bad revision is: changeset: 2305:fbc9c3f7befc user: mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f date: Sun Jan 27 09:47:48 2013 +0000 summary: asdf-2.26.143.1: pre asdf-2.27 plus workaround for SETF autoloader problems. }}} which corresponds to http://trac.common-lisp.net/armedbear/changeset/14362 . -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/311> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 7

[armedbear-ticket] [armedbear] #312: BORDEAUX-THREADS-TEST::CONDITION-VARIABLE hangs
by armedbear 25 Mar '13

25 Mar '13

#312: BORDEAUX-THREADS-TEST::CONDITION-VARIABLE hangs ---------------------------------------------------+------------------------ Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.2.0 Component: (A)MOP | Version: 1.2.0-dev Keywords: quicklisp-regression bordeaux-threads | ---------------------------------------------------+------------------------ [http://news.gmane.org/gmane.lisp.armedbear.devel Stellian notes that] after loading BORDEAUX-THREADS via Quicklisp, the following test hangs the invoking thread: {{{ (fiveam:run 'bordeaux-threads-test::condition-variable) }}} Problem does not appear to exist with abcl-1.1.0 -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/312> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0