- Oct 20, 2011
-
-
Francois-Rene Rideau authored
Indeed, at least on ABCL, the same binaries can run on either. On other implementations, the same may or may not hold for FASLs.
-
- Oct 19, 2011
-
-
Francois-Rene Rideau authored
-
- Oct 18, 2011
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
test/script-support.lisp: cl-user::native-namestring already defined in SBCL (imported from sb-ext); don't try to redefine it.
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- Oct 17, 2011
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- Oct 13, 2011
-
-
Francois-Rene Rideau authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
1. Format ACL shell-command output in the same way as other lisp implementations'. 2. Fix CLISP handling of exit status.
-
Robert P. Goldman authored
bumping version.
-
- Oct 12, 2011
-
-
Francois-Rene Rideau authored
-
- Oct 10, 2011
-
-
Francois-Rene Rideau authored
break things differently, giving user more control when things break. Document somewhat the mess that is asdf:run-shell-command, and recommend xcvb-driver:run-program/process-output-stream as a replacement. Also, rename some testing targets in the Makefile, update testing status. Finally, hush cmucl.
-
- Oct 09, 2011
-
- Oct 07, 2011
-
-
Francois-Rene Rideau authored
Thanks to Andreas Fuchs http://boinkor.net/archives/2011/10/a-weird-problem-with-asdf-on-nfs.html
-
- Oct 06, 2011
-
-
Francois-Rene Rideau authored
Thanks again to Sergey Katrevich for his comments.
-
Francois-Rene Rideau authored
hoping to fix a reported double-compilation bug.
-
- Oct 02, 2011
-
-
Francois-Rene Rideau authored
-
- Sep 25, 2011
-
-
Francois-Rene Rideau authored
to increase chances of successful pathname parsing in defsystem.
-
Francois-Rene Rideau authored
-
- Sep 14, 2011
-
-
Francois-Rene Rideau authored
ECL on Darwin notably doesn't have the :unix feature.
-
- Sep 13, 2011
-
-
Francois-Rene Rideau authored
-
- Sep 12, 2011
-
-
Francois-Rene Rideau authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
- Sep 02, 2011
-
-
Robert P. Goldman authored
Thanks to Christophe Rhodes for suggestions. We use REINITIALIZE-INSTANCE to clear out-of-date information out of the slots of COMPONENT objects while they are reused. Two complications presented themselves: 1. Previously, I believe for orthogonality, we would either get an old (reused) COMPONENT or make a new one, but in either case, the handling of initargs was done by REINITIALIZE-INSTANCE. This made it impossible for the REINITIALIZE-INSTANCE methods to "know" that they were in a real sense RE-initializing. At the expense of some code duplication, I broke this sharing, so that now REINITIALIZE-INSTANCE should only be called when we are reusing a COMPONENT, with an exception below... 2. We always need to have a SYSTEM object active for the defsystem we are currently processing. Accordingly, SYSTEM objects will *ALWAYS* be RE-initialized. So the REINITIALIZE-INSTANCE method required a little care (in particular, the SOURCE-FILE slot needed delicate handling.
-
Robert P. Goldman authored
-
Robert P. Goldman authored
Unfortunately, this doesn't work in general because of other problems with the reuse of pre-existing SYSTEM COMPONENT objects.