- 30 Jan, 2014 3 commits
-
-
-
WILD.PATHNAMES.1 normalization problems were fixed by relaxing semantics on resolving symlinks in CL:DIRECTORY calls.
-
The default for the :RESOLVE-SYMLINKS keyword to CL:DIRECTORY has changed from T to nil, meaning that naked DIRECTORY calls should never return an error for dangling symlinks. Thanks to Marco Antoniotti, Alan Ruttenberg, and Alessio Stallo for clarifying a reasonable position vis a vis ANSI. Addresses <http://abcl.org/trac/ticket/340>.
-
- 27 Jan, 2014 4 commits
-
-
- 26 Jan, 2014 2 commits
-
-
- 25 Jan, 2014 4 commits
-
-
JDK 7(?) changed the default timeout for sockets to 0, which means infinity, which is probably a bad idea when dealing with I/O on the Inner-tubes. Restore the failing tests in ABCL-TEST-LISP: the test suite bombs, but not as catastrophically.
-
Tests are still explicitly chosen via the nested <arg> to the '//abcl.test.java/java@' element at build.xml:940 ff. The test in org.armedbear.lisp.util.HttpHeadTest currently hangs (!) the executing VM, a high priority item for abcl-1.3.0. The problem lies in a hanging read in the JVM system classes that previously didn't exist when accessing the ZipCache.get(url) API for the second time. Users are advised to call SYSTEM:DISABLE-ZIP-CACHE until this behavior is fixed.
-
The java.lang.ClassLoader of the org.lisp.armedbear.Main class is used to find a place to guess at where `abcl-contrib.jar' may be located. TODO: load from http location. TODO: find abcl-contrib-m.n.p[-extra-stuff.jar as well.
-
-
- 22 Jan, 2014 2 commits
-
-
-
Loading still borked (q.v. what should SYS::FIND-SYSTEM-JAR do when there is no `abcl.jar'?
-
- 19 Jan, 2014 2 commits
-
-
From Olof-Joachim Frahm. Additional options for the relevant Maven plugin may be found at <http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html>/
-
Thanks to Anton Vodonosov. See <http://abcl.org/trac/ticket/342>.
-
- 16 Jan, 2014 3 commits
-
-
-
Something is seriously borked with loading fasls via HTTP. Currently, trying to get a jdb version of ABCL running under Netbeans, connected to via SLIME to debug this.
-
From Theam Yang Chew, who writes on http://article.gmane.org/gmane.lisp.armedbear.devel/3059: Hi all, I inadvertently discovered some bugs in the gray-streams implementation due to a stale flexi-streams that did not get upgraded properly. There were quite a few things that needed tidying - the type checking using EQ is wrong. Also, after trying to hunt around CLHS, I think BYTE is not a CL type (though I may be mistaken). This could be a reflection of some Corman Lisp specific feature in the past (Yes! These bugs seem to have been around ABCL for that long!) Some test examples (avoiding flexi-streams or other dependencies) ;; ----- setup (require 'gray-streams) (defclass test-gray-binary-input-stream (gray-streams:fundamental-binary-input-stream) ()) (defclass test-gray-character-input-stream (gray-streams:fundamental-character-input-stream) ()) (let ((bytes (list 65 66 67 68 69)) (pos -1)) (defmethod gray-streams::stream-read-byte ((stream test-gray-binary-input-stream)) (elt bytes (mod (incf pos) 5)))) (let ((chars (list #\A #\B #\C #\D #\E)) (pos -1)) (defmethod gray-streams::stream-read-char ((stream test-gray-character-input-stream)) (elt chars (mod (incf pos) 5)))) ;; ----- (let ((s (make-instance 'test-gray-binary-input-stream))) (loop repeat 10 collect (read-byte s))) => (65 66 67 68 69 65 66 67 68 69) (let ((arr (make-array 10 :initial-element nil))) (list (read-sequence arr (make-instance 'test-gray-binary-input-stream) :start 2 :end 7) arr)) Expected (7 #(NIL NIL 65 66 67 68 69 NIL NIL NIL)), but got an error instead, ... no applicable method... I guess implementors of gray streams would normally define both read-byte & read-sequence. But ABCL's default/fallback method does try to support binary streams, it just isn't being dispatched on the right class. Also, read-sequence should return the "final" array index, not the number of bytes/characters read. Similarly, write-sequence needs to do its work, then return the sequence itself. Attached is a patch with what I hope are the required fixes, please review. Two additional notes, 1. Even after loading my proposed fixes, I'd would still get this, which is ok, but the error message is not obvious enough. This is actually a method not found error, not a type error. There appears to be some type guessing going on, so perhaps the message should indicate failure to dispatch on STREAM or similar. (gray-streams::stream-element-type (make-instance 'test-gray-binary-input-stream)) The value #<TEST-GRAY-BINARY-INPUT-STREAM {500BBBF9}> is not of type STREAM. [Condition of type TYPE-ERROR] So we just need something like this, (defmethod gray-streams::stream-element-type ((stream test-gray-binary-input-stream)) '(unsigned-byte 8)) 2. I also don't understand this snippet in the original code, converting unsigned-bytes/integers (basically the wrong type) to a character? (#+nil ccl:int-char code-char (elt sequence n)) Of course, after patching the above, I discovered that re-compiling flexi-streams got rid of my particular set of problems :-)
-
- 11 Jan, 2014 1 commit
-
-
- 09 Jan, 2014 2 commits
-
-
From ferada on #abcl: toString() should be caught, otherwise abcl just stops http://paste.lisp.org/display/140719.
-
On #abcl, <ferada> notes "if it's correct that T is passed to java methods not as native 'true', then i think jss:get-java-field needs a fix like <http://paste.lisp.org/display/140832>." Lisp 'T' should be a synonym for Java 'true' in method calls. I think it worked as such once, and should again In the longer term, all the accesibility stategy Java language checks should happen in the JAVA package with the possibility setting a per-thread special variable that enforces the JVM policy.
-
- 05 Jan, 2014 5 commits
-
-
-
Latest test results "Java_HotSpot(TM)_64-Bit_Server_VM-Oracle_Corporation-1.7.0_45-b18" on "x86_64-Mac_OS_X-10.9.1".
-
-
-
-
- 04 Jan, 2014 1 commit
-
-
BUNDLE-OP is still borked.
-
- 03 Jan, 2014 1 commit
-
-
To use slime, ensure the directory "~/.asdf-install-dir/systems" exits, and symlink `swank.asd` from a SLIME installation into it. Start the "slime" Netbeans configuration: when you see the "Swank started at port: 4005." message, you may then use Emacs M-x slime-connect to attach to the ABCL instance running in Netbeans. An improvement might to be to randomize the port given to SWANK:CREATE-SERVER somehow. Updated artifacts to Netbeans 7.4.
-
- 27 Dec, 2013 1 commit
-
-
Throw intelligible errors from problems encountered by SHARPSIGN-DOT macros passed through '--eval' arguments. Fixes #334.
-
- 05 Dec, 2013 2 commits
-
-
Fixes loading of the lsw2 util system by normalizing ABCL-ASDF:JAR-FILE components whose pathname NAME component ends in ".jar".
-
-
- 24 Nov, 2013 1 commit
-
-
Pascal Bourguingon.
-
- 10 Nov, 2013 1 commit
-
-
- 09 Nov, 2013 3 commits
-
-
-
-
Added recent trunk ansi-compiled, ansi-interpreter results. A few (~10) new regressions that need to be hunted down.
-
- 02 Nov, 2013 1 commit
-
-
ASDF 3.0.3.0.1 is ASDF 3.0.3 with a small fix for UIOP/UTILITY:ENSURE-FUNCTION so that functions may be used with output translations.
-
- 01 Nov, 2013 1 commit
-
-
Muffle warning of SYS:SHA256 when used for single file.
-