- Jan 21, 2014
-
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
The behavior of OPERATION has changed: previously it would act roughly like LOAD-OP, and automatically have dependencies, but now that behavior has been removed in a clean-up. In order to support programmers, we attempt to detect programmer-defined OPERATION subclasses and signal an error if we believe they are unpatched. The new dependency-handling is implemented in the classes DOWNWARD-OPERATION, UPWARD-OPERATION, SIDEWAY-OPERATION, SELFWARD-OPERATION, and the newly-added NON-PROPAGATING-OPERATION. To detect unpatched OPERATION classes, when we are instantiating an OPERATION, we check to make sure it has one of the above classes as a superclass. If it does not, we raise a continuable error. This is done in an INITIALIZE-INSTANCE :BEFORE method on OPERATION. We considered trying to detect the definition of OPERATION subclasses, but because the MOP is not standard, that approach was rejected as infeasible. Add NON-PROPAGATING-OPERATION as superclass where needed. Further checks and some documentation. Thanks to Fare for advice. Check that no OPERATION is both propagating and non-propagating. Thanks to Fare for the suggestion.
-
Robert P. Goldman authored
Added INITIALIZE-INSTANCE that checks for operations that have no specified dependency propagations. Also added NON-PROPAGATING-OPERATION as a way to specify that an OPERATION subclass /intentionally/ performs no dependency propagation.
-
Robert P. Goldman authored
It turns out it's only the BASIC-FASL-OP, not all the BUNDLE-OPs, that's broken on Mac OSX with ABCL and ECL. Refined the check.
- Jan 20, 2014
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Robert P. Goldman authored
Merge branch 'bundle-op-warn'.
-
Robert P. Goldman authored
Warning from removing unreachable code caused build failures on some lisp implementations.
-
Robert P. Goldman authored
Currently, on Mac OSX, neither ABCL nor ECL passes the bundle-test, so on these platform x implementation pairs, we issue a continuable error when trying to use the BUNDLE-OP.
-
- Jan 18, 2014
-
-
ssh://common-lisp.net/project/asdf/public_html/asdfRobert P. Goldman authored
Some comments, etc. as yet unpushed.
-
Robert P. Goldman authored
-
- Jan 16, 2014
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- Jan 15, 2014
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- Jan 14, 2014
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
Also decline to "upgrade" to very same version, but without warning. Add a regression test. You can see the test fail with old versions, with e.g. cat build/asdf-3.0.3.lisp > build/asdf.lisp ; make t l=ccl t=test-sysdef-asdf.script Also tweak ensure-gethash to return two values, and add tests.
-
- Jan 09, 2014
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
Remove trace on clisp
-
- Jan 08, 2014
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
because 2.32.13 renamed a slot, but we don't provide an according method on update-instance-for-redefined-class.
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
(Why was it introduced in 2.26.136, anyway?)
-
Francois-Rene Rideau authored
Do upgrade tests in reverse chronological order for more relevance.
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
(I suppose the reason it isn't is because that would make for complex decision rules in case of conflicted multiple inheritance)
-