armedbear-ticket

armedbear-ticket@common-lisp.net

633 discussions

[armedbear] #456: SYSTEM:AVAILABLE-ENCODINGS symbols strangeness
by armedbear 01 Apr '18

01 Apr '18

#456: SYSTEM:AVAILABLE-ENCODINGS symbols strangeness ----------------------+--------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: minor | Milestone: 1.6.0 Component: other | Version: Keywords: | Parent Tickets: ----------------------+--------------------------- In https://github.com/armedbear/abcl/issues/82 Robert Dodier reports I see that SYSTEM:AVAILABLE-ENCODINGS returns a list of symbols which represent the various encodings that are discovered via Charset.availableCharsets. That's great, but the symbols are apparently not interned in the keyword package, so it makes it somewhat confusing to determine whether a given encoding is on the list. e.g. {{{(member :utf-16 (system:available-encodings))}}} returns NIL, although looking at the list, you can see that {{{:UTF-16}}} is there. Confusingly, {{{{(mapcar #'symbol-package (system:available- encodings))}}}} shows that all symbols are in the keyword package, but {{{(find-symbol "UTF-16" :keyword)}}} returns NIL. I believe the problem is that {{{availableEncodings}}} in src/org/armedbear/lisp/Stream.java says, in part, (at line 399 in the current version) {{{ new Symbol(charset, PACKAGE_KEYWORD) }}} but I think more appropriate would be {{{ PACKAGE_KEYWORD.intern(charset) }}} Here is a patch which implements that change, and fixes the bug, from what I can tell. {{{ Index: src/org/armedbear/lisp/Stream.java =================================================================== --- src/org/armedbear/lisp/Stream.java (revision 15113) +++ src/org/armedbear/lisp/Stream.java (working copy) @@ -396,7 +396,7 @@ SortedMap<String, Charset> available = Charset.availableCharsets(); Set<String> encodings = available.keySet(); for (String charset : encodings) { - result.add(new Symbol(charset, PACKAGE_KEYWORD)); + result.add (PACKAGE_KEYWORD.intern (charset)); } return result; } }}} -- Ticket URL: <http://abcl.org/trac/ticket/456> armedbear <http://abcl.org> armedbear

1 0

[armedbear] #455: Order of evaluation in expression with BOOLE in compiled code
by armedbear 04 Oct '17

04 Oct '17

#455: Order of evaluation in expression with BOOLE in compiled code ----------------------+---------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: Component: (A)MOP | Version: Keywords: | Parent Tickets: ----------------------+---------------------- {{{ (eval '(let ((a 15)) (boole boole-2 (logior 0 (setf a 14)) a))) ==> 14 (eval (funcall (compile nil '(lambda () (let ((a 15)) (boole boole-2 (logior 0 (setf a 14)) a)))))) ==> 15 }}} -- Ticket URL: <http://abcl.org/trac/ticket/455> armedbear <http://abcl.org> armedbear

1 0

[armedbear] #454: Compile problems with TAGBODY
by armedbear 04 Oct '17

04 Oct '17

#454: Compile problems with TAGBODY ----------------------+------------------------ Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.6.0 Component: compiler | Version: Keywords: | Parent Tickets: ----------------------+------------------------ {{{ (compile nil '(lambda () (tagbody (catch 'c 100)))) ==> COMPILE-TAGBODY: tag not found: 100 [Condition of type SIMPLE-ERROR] }}} c.f. <https://github.com/armedbear/abcl/issues/70> -- Ticket URL: <http://abcl.org/trac/ticket/454> armedbear <http://abcl.org> armedbear

1 0

[armedbear] #453: Compiler failure with stack inconsistency
by armedbear 04 Oct '17

04 Oct '17

#453: Compiler failure with stack inconsistency ----------------------+------------------------ Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.6.0 Component: compiler | Version: Keywords: | Parent Tickets: ----------------------+------------------------ Paul Dietz reports in <https://mailman.common-lisp.net/pipermail /armedbear-devel/2017-October/003884.html> {{{ (defparameter *abcl1* '(lambda (a) (declare (optimize (debug 0) (compilation-speed 1) (speed 2) (space 3) (safety 1))) (ash 0 (bit #*0100 (catch 'ct7 a))))) (defun test1 () (let ((fn (compile nil *abcl1*))) (mapcar fn '(0 1 2 3)))) (test1) ==> ; Caught ERROR: ; Stack inconsistency detected in <unknown> at index 40: found 2, expected 0. }}} c.f. <https://github.com/armedbear/abcl/issues/69> -- Ticket URL: <http://abcl.org/trac/ticket/453> armedbear <http://abcl.org> armedbear

1 0

[armedbear] #452: Pathname functions do the wrong thing when faced with actual filename with embedded asterisk
by armedbear 12 Sep '17

12 Sep '17

#452: Pathname functions do the wrong thing when faced with actual filename with embedded asterisk ----------------------+---------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: Component: (A)MOP | Version: Keywords: | Parent Tickets: ----------------------+---------------------- From <https://github.com/armedbear/abcl/issues/63> In a shell: {{{ touch /tmp/* (probe-file "/tmp/") ; Evaluation aborted on #<FILE-ERROR {7DF4B809}>. CL-USER> (probe-file "/tmp/\") ; Evaluation aborted on #<FILE-ERROR {4D5E9779}>. CL-USER> (probe-file "/tmp/%2A") nil CL-USER> (probe-file "file:///tmp/%2A") ; Evaluation aborted on #<FILE-ERROR {7DF4B809}>. }}} The error is: Bad place for a wild pathname. I had a quick look to see how this could be repaired, but wasn't sure what the right approach is. This stackoverflow answer suggests using "\" as a quote, which is probably the best solution, and would be compatible with what Clozure CL, SBCL and LispWorks do. I also think the percent escaped character should be made to work. The specific screw case I had was that there was an accidentally created file with a "*" in a directory that was being scanned for ASDF's system registry, which crapped out because the directory function returned the "*" pathname, and subsequently did a probe on the file. -- Ticket URL: <http://abcl.org/trac/ticket/452> armedbear <http://abcl.org> armedbear

1 1

[armedbear] #451: DIRECTORY errors with wildcard directory
by armedbear 24 Jul '17

24 Jul '17

#451: DIRECTORY errors with wildcard directory -------------------------+------------------------ Reporter: mevenson | Owner: Type: defect | Status: new Priority: minor | Milestone: 1.6.0 Component: interpreter | Version: Keywords: pathname | Parent Tickets: -------------------------+------------------------ In <https://mailman.common-lisp.net/pipermail/armedbear- devel/2017-July/003870.html>, Mark Cox notes that {{{ (directory (merge-pathnames (make-pathname :directory '(:relative :wild)) (user-homedir-pathname))) }}} errors with {{{ The value NIL is not of type (OR PATHNAME STRING FILE-STREAM SYSTEM:JAR-STREAM SYSTEM:URL-STREAM). [Condition of type TYPE-ERROR] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread. Backtrace: 0: (INVOKE-DEBUGGER #<TYPE-ERROR {7EA9D89E}>) 1: org.armedbear.lisp.Lisp.error(Lisp.java:382) 2: org.armedbear.lisp.Lisp.type_error(Lisp.java:435) 3: (PATHNAME NIL) 4: (PATHNAME-MATCH-P "adbkey" NIL) 5: (DIRECTORY #P"/Users/evenson/*/") }}} -- Ticket URL: <http://abcl.org/trac/ticket/451> armedbear <http://abcl.org> armedbear

1 1

[armedbear] #450: Structure redefinition warning for closure-common
by armedbear 26 Jun '17

26 Jun '17

#450: Structure redefinition warning for closure-common ----------------------+------------------------ Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.6.0 Component: java | Version: Keywords: | Parent Tickets: ----------------------+------------------------ From <https://github.com/armedbear/abcl/issues/59>: <https://github.com/mcna/closure-common> fails to load properly because the xstream structure causes a redefinition failure, the reason being that the slot buffer of type {{{(simple-array buffer-byte (*))}}} (which is also what's in the FASL, {{{(#5=SYSTEM::DEFSTRUCT-SLOT-DESCRIPTION BUFFER #6=0 XSTREAM-BUFFER +NULL-BUFFER+ (#7=SIMPLE-ARRAY BUFFER-BYTE (#8=*)) #2# ))}}} has the expanded type {{{(SIMPLE-ARRAY (INTEGER 0 65535) (*))}}} loaded in the runtime (c.f. {{{(nth 0 (system::dd-slots (get 'runes::xstream 'system::structure-definition))))}}}. {{{ Structure redefinition not supported in DEFSTRUCT for XSTREAM [Condition of type PROGRAM-ERROR] Restarts: 0: [TRY-RECOMPILING] Recompile xstream and try loading it again ... Backtrace: ... 4: (ERROR PROGRAM-ERROR :FORMAT-CONTROL "Structure redefinition not supported ~ in DEFSTRUCT for ~A" :FORMAT-ARGUMENTS (RUNES:XSTREAM)) 5: (SYSTEM:COMPILER-DEFSTRUCT RUNES:XSTREAM :CONC-NAME #:XSTREAM- :DEFAULT-CONSTRUCTOR RUNES::MAKE-XSTREAM/LOW ...) }}} -- Ticket URL: <http://abcl.org/trac/ticket/450> armedbear <http://abcl.org> armedbear

1 0

[Armedbear-ticket] [armedbear] #384: Binary release has no invocation wrapper
by armedbear 15 Jun '17

15 Jun '17

#384: Binary release has no invocation wrapper ----------------------+----------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.4.0 Component: other | Version: 1.4.0-dev Keywords: | ----------------------+----------------------- ABCL binary release should contain an invocation wrapper ('abcl{,.bat}'). -- Ticket URL: <http://abcl.org/trac/ticket/384> armedbear <http://abcl.org> armedbear

1 1

[armedbear] #422: SYSTEM:RUN-PROGRAM does not work on Java 5/6
by armedbear 15 Jun '17

15 Jun '17

#422: SYSTEM:RUN-PROGRAM does not work on Java 5/6 ------------------------------------------------+------------------------ Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.5.0 Component: interpreter | Version: 1.4.0 Keywords: cffi sys:run-progrom java-5 java-6 | Parent Tickets: ------------------------------------------------+------------------------ In chasing down the errors with CFFI on CL-TEST-GRID <https://mailman .common-lisp.net/pipermail/armedbear-devel/2016-October/003719.html>, I have found that the [java.lang.ProcessBuilder$Redirect][] interface used by Elias and Olof to extend SYS:RUN-PROGRAM for different types of I/O abstractions was introduced with Java 7, and will hence not work on earlier Java implementations. [java.lang.ProcessBuilder$Redirect]: https://docs.oracle.com/javase/8/docs/api/java/lang/ProcessBuilder.Redirect… Invoking ABCL-ASDF:ENSURE-MVN-VERSION, the following form causes the error {{{ (JFIELD "java.lang.ProcessBuilder$Redirect" "INHERIT") }}} TODO: investigate the Java 6 APIs to see if there is a way to do I/O redirection with backwards compatibility. I currently suspect that there is no way to support Java 5/6 for this usage, which is why we never implemented I/O redirection previously. There is undoubtedly a way re-write the SYS:RUN-PROGRAM interface so that we may invoke a process to read its output as a string in Java 5/Java 6, as it worked before. But we will have to figure out a way to advertise the different features of SYS:RUN-PROGRAM depending on the hosting VM. Longer term, we may want to deprecate Java 5/6, but I would really have the compiler emit Java 7-compatible bytecode (mainly by passing the Java 6 verification process) before we begin that. -- Ticket URL: <http://abcl.org/trac/ticket/422> armedbear <http://abcl.org> armedbear

1 9

Re: [armedbear] #326: abcl cannot be compiled with Java5
by armedbear 15 Jun '17

15 Jun '17

#326: abcl cannot be compiled with Java5 ---------------------------+------------------------ Reporter: mevenson | Owner: unassigned Type: defect | Status: closed Priority: blocker | Milestone: 1.6.0 Component: java | Version: 1.3.0-dev Resolution: wontfix | Keywords: Parent Tickets: | ---------------------------+------------------------ Changes (by mevenson): * status: assigned => closed * resolution: => wontfix Comment: Java 5 is no longer supported. -- The Mgmt. -- Ticket URL: <http://abcl.org/trac/ticket/326#comment:8> armedbear <http://abcl.org> armedbear

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
64
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-ticket