- 04 May, 2018 1 commit
-
-
Robert P. Goldman authored
-
- 07 Mar, 2018 2 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
-
- 01 Mar, 2018 1 commit
-
-
Peter Housel authored
These changes add support for the Mezzano operating system and its Common Lisp implementation. They are based on changes originally developed by Henry Harrington against ASDF 3.1.7.
-
- 20 Feb, 2018 1 commit
-
-
Robert Goldman authored
-
- 19 Feb, 2018 1 commit
-
-
Robert Goldman authored
-
- 17 Feb, 2018 2 commits
-
-
Eric Timmons authored
SBCL has been getting aggresive with checking arguments to functions. For some reason (as of SBCL 1.4.1), setting the package source location in define-package seems to trigger a source translation for the apply form that ends up producing (many) compilation notes that the arguments to ensure-package in the keyword positions are not constant, weakening keyword argument checking. We can get around that, however, by using a funcall directly.
-
Eric Timmons authored
Tested on SBCL 1.4.4. If sb-c:source-location is evaluated during macro expansion, then the source location will always point to asdf.lisp (inside the define-package macro). If it is evaluated after macro expansion, it points to the right place.
-
- 16 Jan, 2018 1 commit
-
-
Robert Goldman authored
-
- 18 Dec, 2017 1 commit
-
-
Robert Goldman authored
-
- 17 Dec, 2017 1 commit
-
-
Francois-Rene Rideau authored
Enhance define-package so SBCL can locate the source-location of the package.
-
- 12 Dec, 2017 1 commit
-
-
Francois-Rene Rideau authored
-
- 14 Nov, 2017 1 commit
-
-
Robert Goldman authored
-
- 26 Oct, 2017 2 commits
-
-
Robert Goldman authored
-
-
- 20 Oct, 2017 1 commit
-
-
Francois-Rene Rideau authored
Restore backward compatibility with older versions of ASDF (before 3.3.0) by renaming stamp< and its friends to timestamp<, etc. Sometime in the lead-up to ASDF 3.3.0, I changed the encoding of infinities from NIL is -infinity and T is +infinity to T is -infinity and T is +infinity which made the code notably nicer on the ASDF side, because file-write-date would return directly the correct result instead of having to constantly switch between inverse conventions. However --- big mistake --- I kept the same function name, after checking that the functions had no user in Quicklisp, no one who had ever discussed them but me, and no documentation before 3.2.0 except a single comment line for the entire family of functions. This doesn't matter as long as ASDF and UIOP are kept in synch, but such is not the case with Quicklisp, where Xach both welcomes recent UIOP releases but refuses to include updates to ASDF itself. Then, loading a new UIOP with reverse conventions totally confuses the old ASDF, and causes spurious rebuilds of everything after UIOP is loaded -- multiple times if present in multiple phases (that and slower build times is how Xach noticed the bug). The solution adopted is to give a new name to the functions with a different convention -- timestamp< instead of stamp<, and so on. Therefore, the new ASDF 3.3.1 will expect the new convention from UIOP 3.3.1, that will no longer overwrite the functions from ASDF 3.2.1 and older with backward-incompatible variants. If an old ASDF 3.2.1 or earlier loads a newer UIOP 3.3.1 or later, it will keep using the old functions: the symbols for these functions will be uninterned, but the values for these functions which won't be clobbered anymore. Backward compatibility is a strong requirement not to to break lightly, not even in a subtle way, not even if "nobody else is using it" --- an older version of ASDF is already "somebody else" with respect to UIOP.
-
- 12 Oct, 2017 1 commit
-
-
Robert Goldman authored
-
- 06 Oct, 2017 2 commits
-
-
Robert Goldman authored
-
Francois-Rene Rideau authored
-
- 11 Sep, 2017 1 commit
-
-
Elias Pipping authored
The next ECL release after 16.1.3 will have :resumed. -> See also https://gitlab.com/embeddable-common-lisp/ecl/issues/273 Moreover (even though these lisps have dedicated process-alive-p functions and are thus not currently affected: The next SBCL release after 1.3.21 will have :continued -> See also https://sourceforge.net/p/sbcl/sbcl/ci/5ff75f6/ The next CMUCL release after 21b will have :continued -> See also cmucl/cmucl#41
-
- 06 Sep, 2017 5 commits
-
-
Elias Pipping authored
-
Elias Pipping authored
-
Elias Pipping authored
-
Elias Pipping authored
-
Elias Pipping authored
-
- 02 Sep, 2017 1 commit
-
-
Elias Pipping authored
-
- 01 Sep, 2017 2 commits
-
-
Robert Goldman authored
At least versions of lispworks fail on DEFTYPE nested in EVAL-WHEN :COMPILE-TOPLEVEL. This removes that on Lispworks.
-
Elias Pipping authored
This warning causes the test suite not to compile -- an issue that was reported by Chun Tian (user binghe on github).
-
- 30 Aug, 2017 1 commit
-
-
Robert Goldman authored
Update comment based on Chun Tian's RMCL test. No code change.
-
- 24 Jul, 2017 2 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
Group the commands in ( parentheses ) including the optional chdir. Update the test-run-program.script.
-
- 21 Jul, 2017 1 commit
-
-
Daniel Kochmański authored
It is wrong to call this function. If :init-name is not supplied, or NIL ECL will compute the init name itself (it is not a new mechanism). Enabling specifying init-name makes it possible to build static and shared libraries with known initialization function (important, when CL module is linked with bigger C/C++ project outside ASDF). If :init-name is NIL, it will default to compute-init-name internally. Calling explicitly is not guaranteed to work in the future (internal mechanism).
-
- 20 Jul, 2017 3 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
Do not perform an action twice in a session. Introduce three status bits that every action has in a given session, in addition to the stamp: KEEP-P (from previous session), DONE-P (and up-to-date, in this image), NEED-P (needed in this image as part of this session). BACKWARD INCOMPATIBILITY: Invert the meaning of NIL and T for STAMP, so that NIL means out-of-date. This makes our code conceptually nicer, and no one in Quicklisp uses our stamps, anyway. Still, beware.
-
Francois-Rene Rideau authored
-
- 06 Jul, 2017 1 commit
-
-
Rommel MARTINEZ authored
-
- 23 May, 2017 1 commit
-
-
Francois-Rene Rideau authored
This addresses an issue in sbcl-1.3.17-59-g1069e99c0 whereby some strings used in the warnings are base-string that can't be printed readably without *read-eval* being t.
-
- 13 Apr, 2017 1 commit
-
-
Francois-Rene Rideau authored
This reverts commit b3622011. The commit was based on the wrong assumption that terminate-process would kill a Unix thread (a la pthread_create) rather than subprocess (a la fork+execve).
-
- 03 Apr, 2017 1 commit
-
-
Francois-Rene Rideau authored
-
- 02 Apr, 2017 1 commit
-
-
Francois-Rene Rideau authored
-