- Sep 17, 2016
-
-
Francois-Rene Rideau authored
Make ENSURE-DIRECTORY-PATHNAME and TRUENAME* more robust in case MAKE-PATHNAME throws an error when trying to synthetize a pathname with components that the implementation considers invalid. Uncomment the proper definition of LISP-IMPLEMENTATION-DIRECTORY on CLISP, which now doesn't break asdf-pathname-test anymore.
-
- Sep 16, 2016
-
-
Francois-Rene Rideau authored
-
- Sep 15, 2016
-
-
Robert Goldman authored
Recent patch relied on MKCL:GIT-DESCRIBE-THIS-MKCL, which is not uniformly available.
-
Elias Pipping authored
Rather than "1.1.10" for the current HEAD, which is 155 commits head of 1.1.9 and will probably eventually be called 1.1.10, the output will now be "1.1.9.155-fc50d00"; the same git-described-inspired format that is used by SBCL. The function mkcl:git-describe-this-mkcl is only available in very recent versions of MKCL; in particular, not in vanilla 1.1.9
-
Elias Pipping authored
The way that lisp-version-string is written, it will fall back to lisp-implementation-version unless a platform-specific override is provided. Since the body of lisp-version-string uses (car (list #+foo exp1 exp2)) rather than (or #+foo exp1 exp2) it is theoretically possible that lisp-version-string would return NIL if that's what exp1 evaluates to, which would not also be returned by lisp-implementation-version, which it previously would not have. Such behaviour would qualify as a bug in lisp-version-string, though.
-
Elias Pipping authored
The snippet (format nil "~A-~A" (lisp-implementation-version) (core:lisp-implementation-id)) would generate something as superfluous as "cclasp-boehm-0.4.0-1024-g3533831-3533831"
-
Elias Pipping authored
-
- Sep 12, 2016
-
- Sep 11, 2016
-
-
Francois-Rene Rideau authored
- Sep 10, 2016
-
-
Daniel Kochmański authored
- Sep 09, 2016
-
-
Elias Pipping authored
Whitespace changes were intentionally left out of the previous commit to keep it readable.
-
Elias Pipping authored
This allows the :setf of with-program-*put to complete so that in particular, any remaining output will be written
- Sep 08, 2016
-
-
Daniel Kochmański authored
- Sep 07, 2016
-
-
Elias Pipping authored
-
- Sep 05, 2016
-
-
Elias Pipping authored
-
- Sep 03, 2016
-
- Sep 02, 2016
-
-
Elias Pipping authored
The functions that can allegedly be called on clasp in analogy to ecl do not exist. Calling %run-program would yield a cryptic error prior to this change because `apply` is called with a list of arguments but no function.
-
Elias Pipping authored
The difference between :overwrite (the former default) and :supersede is only that the latter should not lead to an error if the file does not exist. There is plenty of support for :supersede behaviour (not necessarily under that name) but not for :overwrite behaviour. Hence we make it the default and add a normaliser. Since normalisation is currently only necessary for CLISP and CLISP only has :if-output-exists support (not :if-error-output-exists or :if-input-does-not-exist), we only translate :if-output-exists for now.
-
Elias Pipping authored
On platforms where %wait-process-result is not supported, an error is supposed to be raised. Since the error is only raised when the process-info field 'process' is non-nil, on CLISP (where 'process' is always NIL), the function instead behaves like a dummy.
-
Elias Pipping authored
-
Elias Pipping authored
Have wait-process-result save the exit-code in process-info since we cannot retrieve it again later.
-
Elias Pipping authored
By having :process always be a stream on LispWorks 7, we make sure that the process can be killed, have its vital signs checked, and its PID obtained. In a simple and consistent manner. With LispWorks 7, pid-exit-status is no longer available. We need a stream to obtain the exit status. With save-exit-status, we can be sure that we're given one.
-
Elias Pipping authored
-
Elias Pipping authored
Allows for type checking and in-place changes via setf
-
Elias Pipping authored
SBCL's run-program does not currently have an :if-output-does-not-exist keyword (as of 1.3.8). It seems it never did, either, as suggested by the following (superfluous?) feature request https://bugs.launchpad.net/sbcl/+bug/789817 The same applies to :if-error-does-not-exist
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
Thanks to Elias Pipping https://bugs.launchpad.net/asdf/+bug/1604008
-
Francois-Rene Rideau authored
-