Commit 34dd7b9f authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files

Restore deprecated function operation-forced

Undelete this function as a workaround for the large breakage in Quicklisp
due to its still using an old SWANK.

Revert "Remove operation-forced altogether"

This reverts commit 545ab9ff.
parent dbe9942a
......@@ -12,6 +12,7 @@
#:error-component #:error-operation #:traverse
#:operation-on-failure #:operation-on-warnings #:on-failure #:on-warnings
......@@ -47,6 +48,22 @@ or define methods on PREPARE-OP, etc."
;; Old deprecated name for the same thing. Please update your software.
(component-sideway-dependencies component))
(defun* (operation-forced) (operation)
"DEPRECATED. Assume it's (constantly nil) instead -- until it disappears."
;; This function exists for backward compatibility with swank.asd, its only user,
;; that still abuses it as of 2016-10-01.
;; The magic PERFORM method in swank.asd only actually loads swank if it sees
;; that the operation was forced. But it actually fails, badly, in that case.
;; The correctness criterion for a build specification (which is _not_
;; specific to ASDF) requires that the effects of a build step must NOT depend
;; on whether the step was "forced" or not. Therefore it is correct that this
;; method should return constantly the same result. Since returning T currently
;; causes massive failure in SLIME, it shall be constantly NIL.
;; see also
(declare (ignore operation))
;; These old interfaces from ASDF1 have never been very meaningful
;; but are still used in obscure places.
;; In Quicklisp 2015-05, still used by cl-protobufs and clx.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment