- 05 Dec, 2021 1 commit
-
-
Mark authored
@phoe suggested <https://github.com/armedbear/abcl/pull/364/files#r593767261>
-
- 16 Jan, 2021 1 commit
-
-
Mark authored
Addresses <https://github.com/armedbear/abcl/issues/363>.
-
- 28 Nov, 2021 1 commit
-
-
Alejandro Zamora Fonseca authored
- If a symbol is found accessible now is printed without package prefix in all cases
-
- 26 Nov, 2021 1 commit
-
-
https://github.com/armedbear/abcl/issues/407Alejandro Zamora Fonseca authored
improve cl:dribble This version save almost everything to the specified file creating a new internal REPL for dribbling and also ends smoothly when (dribble) is called
-
- 26 Oct, 2021 7 commits
- 19 Oct, 2021 3 commits
-
-
Mark authored
-
Mark authored
c.f. <https://github.com/armedbear/abcl/issues/398>
-
Mark authored
c.f. <https://github.com/armedbear/abcl/issues/399>.
-
- 18 Oct, 2021 1 commit
-
-
Mark authored
This version includes the necessary native shared object trampoline for working under macOS/aarch64 (aka "M1" aka "Apple Silcon".
-
- 17 Oct, 2021 3 commits
-
-
Mark authored
CL+SSL fails under openjdk17 with a segmentation violation for the bad cert test, so place it at the end.
-
Mark authored
Start port to openjdk1[67] Use JAR-PATHNME for implementing through jar entries in order to work on openjdk16/openjdk17. The new implementation is roughly four times slower than the previous version probably because it conses around 100 times more memory.
-
Mark Evenson authored
Use the released LTS Java editions for testing: openjdk8, openjdk11, and openjdk17. TODO: figure out how to signal non-zero condition for individual test suites so they "go green/red" for easier inspection.
-
- 16 Oct, 2021 1 commit
-
-
Mark authored
The code removed in this patch seems to be attempting to adjust for times which occurred after a 32-bit representation of the UNIX epoch would wrap around to zero. This doesn't make much sense as Common Lisp times are clearly defined as an integer number of seconds after 1900. The ansi-test DECODE-UNIVERSAL-TIME.5 now passes. c.f. <https://abcl.org/trac/ticket/443>.
-
- 19 Sep, 2021 2 commits
-
-
Mark authored
-
Mark authored
Removes warnings in openjdk17 compilation. <https://stackoverflow.com/questions/47095474/the-constructors-integerint-doubledouble-longlong-and-so-on-are-deprecat> claims that openjdk9 onwards caches small Integers.
-
- 25 Aug, 2021 1 commit
-
-
Mark authored
The CIs now build and test with openjdk8, openjdk11, and openjdk16.
-
- 17 Sep, 2021 1 commit
-
-
Samuel Hunter authored
Fixes #388, replaces #389. The reader function `stream-error-stream` signals a `type-error` if it's applied to conditions that's typep to `stream-error`, but whose class is a subtype to `stream-error`: ```lisp (define-condition broken-error (stream-error) ()) BROKEN-ERROR (stream-error-stream (make-condition 'stream-error :stream (make-string-input-stream "foo"))) #S(SYSTEM::STRING-INPUT-STREAM) (stream-error-stream (make-condition 'broken-error :stream (make-string-input-stream "foo"))) #<THREAD "interpreter" {2075326}>: Debugger invoked on condition of type TYPE-ERROR The value #<BROKEN-ERROR {75A83798}> is not of type STREAM-ERROR. ``` This fault exists within these reader functions: - file-error-pathname (almost -- instead of a type-error, the function returns NIL instead.) - package-error-package - arithmetic-error-operation - arithmetic-error-operands The fault exists because the Java code checks if its argument is instanceof its respective Java class. So, the method will fail on any conditions defined in CL that subclass these errors. Furthermore, some reader functions only check if they're instanceof StandardObject, which allows any CLOS object to succeed as long as the slot the primitive method is looking for exists: - cell-error-name - type-error-datum - type-error-expected-type Finally, some reader functions exist in standalone Java files, while others reside in its condition's class file, adding to some organizational clutter. This change fills two main jobs: - Standardize all reader functions to the same behavior: If the argument is typep to the right condition, return the right slot value. Otherwise, signal a type error. - Move standalone reader Java code to the files of errors they apply to. As an aside, this change would make ABCL's reader functions conformant to a wave of proposals for WSCL: - https://github.com/s-expressionists/wscl/blob/main/wscl-issues/proposed/cell-error-name-type-error - https://github.com/s-expressionists/wscl/blob/main/wscl-issues/proposed/stream-error-stream-type-error - https://github.com/s-expressionists/wscl/blob/main/wscl-issues/proposed/type-error-datum-type-error - And the rest
-
- 06 Sep, 2021 1 commit
-
-
Kasper Gałkowski authored
Seems to have been copied by mistake from lisp-to-java/Main.java
-
- 24 Aug, 2021 4 commits
- 12 Aug, 2021 1 commit
-
-
- 14 Aug, 2021 1 commit
-
-
Mark authored
Tests <https://abcl.org/trac/ticket/485>
-
- 12 Aug, 2021 2 commits
-
-
Mark authored
(Phil Eaton) I noticed that under the current systems calls like (jstatic "asList" "java.util.Arrays" (jnew-array "int" 0)) works because the signature is java.util.Arrays.asList(T...) but the system didn't support signatures like java.nio.file.Path.of(String first, String... more). This patch adds support for that and makes the "no method found" message easier to understand when calling jstatic with a signature that is not found. <https://github.com/armedbear/abcl/pull/379>
-
Mark authored
-
- 11 Jul, 2021 3 commits
-
-
Mark authored
-
Mark authored
Under ABCL, when loading system definitions from a JAR-PATHNAME, the PARSE-UNIX-NAMESTRING was including the DEVICE in the defaults to MAKE-PATHNAME. This was mostly harmless but fails when (the as yet unlrelease abcl-1.8.1) tightened the definition of JAR-PATHNAME to always have an absolute directory
-
Mark authored
-
- 10 May, 2021 3 commits
-
-
Mark authored
This allows constructs like (jclass "java.lang.Integer[]") to work.
-
Mark authored
Probably broken since the revision of the JAR-PATHNAME merging semantics in abcl-1.8.0. Resolves <https://github.com/armedbear/abcl/issues/372>, <https://abcl.org/trac/ticket/486>.
-
Mark authored
Use abcl.version instead, fixing manifests for jar packaging. The usage of abcl.implementation.version is now deprecated as not working for a long time. The intention was that if a given source tree could be unidentified as being under source control by the presence of given revision control system artifacts, the abcl.implementation.version would contain a version derived from the revision control system. To hack around the non-prescriptive nature of Ant, chains of conditional targets had to be created that while might have once worked for Subversion, were going to get increasingly hairy for Mercurial and Git.
-
- 07 Feb, 2021 1 commit
-
-
daewok authored
-
- 29 Jan, 2021 1 commit
-
-
Olof-Joachim Frahm authored
Not a particularly nice byte vector representation though.
-