- 27 Jun, 2022 1 commit
-
-
Christian Schafmeister authored
The new changes to add support for launch-program break asdf for older clasp versions. This commit fixes that.
-
- 20 Jun, 2022 2 commits
-
-
Christian Schafmeister authored
-
Christian Schafmeister authored
Clasp supports uiop/launch-program. Copied source code from ecl into clasp to support uiop/launch-program so API's between clasp and ecl are identical.
-
- 27 Apr, 2022 1 commit
-
-
Robert Goldman authored
-
- 28 Mar, 2022 2 commits
-
-
Eric Timmons authored
Fix some CI pipeline issues: 1. Do not trigger the standard pipeline and New image pipeline simultaneously. 2. Fix creation of issues when a new image is tested and fails. 3. Pin Clasp to b14e329f49998275579926da2a737885ceb2cea7. Clasp 1.0.0 needs LLVM 13, which means the most logical base image to use is based on Debian Bookworm. However, Bookworm uses the faccessat2 system call, which incorrectly returns EPERM (instead of ENOSYS) on certain versions of Docker. This breaks many things and has been reported to the CLF. See merge request !183
-
Eric Timmons authored
1. Do not trigger the standard pipeline and New image pipeline simultaneously. 2. Fix creation of issues when a new image is tested and fails. 3. Pin Clasp to b14e329f49998275579926da2a737885ceb2cea7. Clasp 1.0.0 needs LLVM 13, which means the most logical base image to use is based on Debian Bookworm. However, Bookworm uses the faccessat2 system call, which incorrectly returns EPERM (instead of ENOSYS) on certain versions of Docker. This breaks many things and has been reported to the CLF.
-
- 23 Feb, 2022 2 commits
-
-
Robert Goldman authored
Expand UIOP:DEFINE-PACKAGE docstring, and fix behavior of `:mix` clauses, which should not have had the defaulting use list. See merge request !205
-
Robert Goldman authored
-
- 14 Feb, 2022 2 commits
-
-
Robert Goldman authored
Adds FAQ item on customizing paths for sources and binaries, fixes typo See merge request !201
-
-
- 20 Jan, 2022 1 commit
-
-
Robert Goldman authored
Add allegro to CI See merge request !204
-
- 18 Jan, 2022 4 commits
-
-
Eric Timmons authored
-
Eric Timmons authored
-
Eric Timmons authored
-
Eric Timmons authored
-
- 17 Jan, 2022 2 commits
-
-
Robert Goldman authored
Refine DEFINE-PACKAGE docstring. See merge request !203
-
Robert Goldman authored
Expand on the use of :UNINTERN keyword argument, based on discussion around issue #85.
-
- 10 Jan, 2022 3 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
Better handling of missing packages in DEFINE-PACKAGE :IMPORT-FROM Closes #98 and #101 See merge request !199
-
Signal a style warning if we `:import-from` using a package that does not exist and an empty symbol list. Remains an error to `:import-from` a package that does not exist with a non-empty symbol list. Add some tests to try and ensure `:uiop/package` and `:uiop/package-local-nicknames` are not modified.
-
- 07 Jan, 2022 2 commits
-
-
Robert Goldman authored
Export name of the PROCESS-INFO class. See merge request !198
-
Robert Goldman authored
Also add brief docstring to tell programmers limits on its use.
-
- 06 Jan, 2022 2 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
make UPGRADE-ASDF return T only if a version number changed See merge request !195
-
- 05 Jan, 2022 10 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
Ensure version slot of preloaded systems is correct after an upgrade Closes #94 See merge request !194
-
Eric Timmons authored
This test has probably been broken for a very long time, but it was missed due to UPGRADE-ASDF returning T all the time. This meant that the first LOAD-OP was performed in a new session, *not* the session created at the top of the file. Once UPGRADE-ASDF was fixed, then the done status of the LOAD-OP was persisted, resulting in the next LOAD-OP being a no op. However, this breakage wasn't immediately apparent because FILE-WRITE-DATE was compared with #'>= and the PLAN was not asserted to actually contain the operations we wanted to see. So on a fast computer (unless you got really unlucky) you'd never see the failed test.
-
-
FIND-SYSTEM may cause the system to be loaded from the file system. REGISTERED-SYSTEM won't load it from the file system, but will return something from the file system if it's already been loaded from there. It's safe to do this as the preloaded systems are always considered to be registered.
-
-
-
Since 3.3.2 / 069cd2a6, the primary system name of a misnamed system is derived from the pathname of the .asd file that defines it, not the name of the system itself. This means that within the same cache session, any operation on a misnamed system will depend on DEFINE-OP for the file where it was already found and will *not* depend on a DEFINE-OP for the "syntactic" primary name. The test test-mutual-redefinition.script has been broken since (at least) then. However, it was missed due to UPGRADE-ASDF always returning T. This resulted in every load-system in this test running with an isolated cache.
-
An effect of UPGRADE-ASDF always returning true is that a nested session was unconditionally started by the :AROUND method on OPERATE. This means that *ASDF-SESSION* was always bound to a session object whenever any real work was being done. Now that UPGRADE-ASDF does not unconditionally return T, it's likely that CLEAR-CONFIGURATION-AND-RETY will be invoked in the first CALL-WITH-ASDF-SESSION on the stack and *ASDF-SESSION* will be bound to NIL. So, check that it's not NIL before we grab its SESSION-CACHE.
-
This is what the docstring says it does. However, it's unconditionally returned T since 2.27 / ab797258.
-
- 24 Dec, 2021 3 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
Merge branch '98-uiop-define-package-signals-a-type-error-when-trying-to-import-from-a-non-existent-package' into 'master' Resolve "UIOP:DEFINE-PACKAGE signals a TYPE-ERROR when trying to IMPORT-FROM a non-existent package" Closes #98 See merge request !197
-
Robert Goldman authored
Resolve "UIOP:DEFINE-PACKAGE signals a TYPE-ERROR when trying to IMPORT-FROM a non-existent package" (#98) The code handling other options to `define-package` used `find-package*`, which (by default) errors if it can't find the package it's looking for. The exception was the code for `:import-from`. This caused cryptic error messages (issue #98) when trying to import from a package that did not exist. Switched to using `find-package*`, added a new exception class, and added a test.
-
- 23 Dec, 2021 2 commits
-
-
Robert Goldman authored
Attila Lendvai's test script for issue 97. See merge request !196
-
Robert Goldman authored
This demonstrates the issue, but only as a test that is expected to fail.
-
- 04 Oct, 2021 1 commit
-
-
Robert Goldman authored
Change image location for CI pipelines See merge request !193
-