- Sep 02, 2016
-
-
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
-
- Aug 27, 2016
-
-
Francois-Rene Rideau authored
When using DIRECTORY, the proper pattern to use to get all files is #p"*" and not #p"*.*" on CLISP and GCL. This is the opposite of other CL implementations, that match everything with #p"*.*" and only files without extension with #p"*", which seems more in line with the CLHS, though counter-intuitive wrt to POSIX. Now the proper pattern to match all files with TRANSLATE-PATHNAME and with logical pathnames is still #p"*.*" or #p"*.*.*". Therefore, we introduce a new parameter *wild-file-for-directory*, as distinguished from *wild-file*, for notable use with DIRECTORY-FILES.
-
Francois-Rene Rideau authored
This make test-logical-pathname.script work on CLISP, despite CLISP bug 677.
- Aug 19, 2016
-
- Aug 18, 2016
-
- Aug 15, 2016
-
-
Robert Goldman authored
Needed for clean compile.
-
- Aug 11, 2016
-
-
Elias Pipping authored
If a process is killed by a signal, sys:reap-os-subprocess will return (0, pid, signal) so that checking the exit code alone does not suffice.
-
Elias Pipping authored
The code for Clasp, Clozure CL, and ECL is there, only the list of implementations in #-(...) was not up-to-date.
-
Elias Pipping authored
Use the public function ccl:external-process-id instead the private ccl::external-process-pid external-process-id has been exported from the ccl packages since at least 2008.
-
Elias Pipping authored
:wait t and :*put :stream cannot be mixed on some platforms but not others.
-
Elias Pipping authored
-
Elias Pipping authored
The system package (si for short) is internal and "never to be used" according to https://common-lisp.net/project/ecl/manual/ch11.html This change does not require testing because (presumably unintentionally) the process-info-pid function generates an error for ECL anyway (to be fixed in a follow-up commit)
-
Elias Pipping authored
Prior to this, %run-command would generate errors such as File #P"/dev/null" already exists.: File exists [errno=17]. Tested with acl-10.0-linux-x86.
-
Elias Pipping authored
-
- Aug 01, 2016
-
-
Robert Goldman authored
Previous method was over-complicated. Now we simply appropriately define the type UIOP:FATAL-CONDITION, and we can do without both UIOP:*FATAL-CONDITIONS* and UIOP::*FATAL-CONDITION-EXCEPTIONS*.
- Jul 25, 2016
-
-
Robert Goldman authored
See https://bugs.launchpad.net/asdf/+bug/1605650 According to the spec, SERIOUS-CONDITIONs are "All conditions serious enough to require interactive intervention if not handled should inherit from the type serious-condition." This is almost exactly the definition of *FATAL-CONDITIONS*, so I substituted SERIOUS-CONDITION for ERROR here. Added exceptions to the set of *FATAL-CONDITIONS* in order to fix test condition handling for CCL. The exceptions permit us to have a class of conditions (e.g., SERIOUS-CONDITION) that has a subclass that is not a FATAL-CONDITION, but that does not have an obvious more specific alternative. The specific example that caused me to add this: On shutdown, CCL signals CCL:PROCESS-RESET, a subclass of SERIOUS-CONDITION. So recent test harness modifications to handle SERIOUS-CONDITIONs caused the test scripts to mistakenly think there were failures because of calls to EXIT-LISP.
- Jul 24, 2016
-
- Jun 27, 2016
-
-
Robert Goldman authored
Mistakenly committed after refilling a comment and emacs refilled it wrong, so that comment was incorrectly not all prefixed by comment characters.
-
- Jun 24, 2016
-
-
Robert Goldman authored
- Jun 11, 2016
-
-
Francois-Rene Rideau authored
Bug found by @axionic on github: on very large directories, directory-files was slow, because it was using remove-duplicates with non-hashable test function #'pathname-equal. But this functionality was only really needed for the purpose of dealing with logical-pathnames, and having a few duplicates in case of wanton symlinks isn't much of an issue.
- May 25, 2016
-
-
Robert Goldman authored
In some cases a subdirectory pathname returned from this function was not a DIRECTORY-PATHNAME (i.e., leaf directory name was in the PATHNAME-NAME, not PATHNAME-DIRECTORY). I used ENSURE-DIRECTORY-PATHNAME to avoid this happening.
-
- Apr 13, 2016
-
-
Robert Goldman authored
-
- Mar 30, 2016
-
-
matthieupeeters authored
-
- Mar 23, 2016
-
-
Robert Goldman authored
-
- Mar 21, 2016
-
- Mar 07, 2016
-
- Feb 27, 2016
-
-
Robert Goldman authored
-
- Feb 25, 2016
-
- Feb 22, 2016
-
- Jan 28, 2016
-
-
Francois-Rene Rideau authored