Commit 6b1918b7 authored by Eric Timmons's avatar Eric Timmons
Browse files

Do not test for sb-eval feature

SBCL 2.0.1 removed :sb-eval from *features* (and added it to an internal
features list). Additionally the #+ reader macro now produces a full warning if
a feature present on the internal features list is tested for.

This commit tests for the presence of sb-kernel:lexical-environment-too-complex
directly instead of looking at the sb-eval feature.
parent 56dc62d5
......@@ -138,7 +138,6 @@ This can help you produce more deterministic output for FASLs."))
"&OPTIONAL and &KEY found in the same lambda list: ~S"
#+sb-eval sb-kernel:lexical-environment-too-complex
sb-grovel-unknown-constant-condition ; defined above.
sb-ext:implicit-generic-function-warning ;; Controversial.
......@@ -149,6 +148,10 @@ This can help you produce more deterministic output for FASLs."))
sb-kernel::redefinition-with-defmacro) ; not exported by old SBCLs
(let ((condition (find-symbol* '#:lexical-environment-too-complex :sb-kernel nil)))
(when condition
(list condition)))
'("No generic function ~S present when encountering macroexpansion of defmethod. Assuming it will be an instance of standard-generic-function.")) ;; from closer2mop
"A suggested value to which to set or bind *uninteresting-conditions*.")
Markdown is supported
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