Eric Marsden <eric.marsden@...> writes:
> | * (lisp-implementation-version)
> | "22.214.171.124-7d40722"
> | * (make-condition '(or program-error type-error))
> | debugger invoked on a SIMPLE-TYPE-ERROR:
> | Bad type argument:
> | (OR PROGRAM-ERROR TYPE-ERROR)
> CLHS: the first argument to MAKE-CONDITION is a type specifier (for a
> subtype of CONDITION).
This rings a bell as one of a small set of PFD ANSI-test failures which
I intentionally did not intend to fix, on the grounds that there was no
real way of doing anything close to The Right Thing. In fact, if you
dig down in the history of
far enough, you may find that it was me who wrote, under "Proposed
changes to the standard"
Issue MAKE-CONDITION-ERROR?: MAKE-CONDITION should be allowed to
signal an error on type arguments that do not name classes, like (or