On Sep 15, 2005, at 13:51, Harald Hanche-Olsen wrote:
> + Christian Nybø <[EMAIL PROTECTED]>:
>
> | CL-USER> (subtypep 'not-a-type-spec t)
> | T
> | T
> | CL-USER>
> |
> | Not quite right, is it?
>
> Well, according to the hyperspec, subtypep cannot signal an exception.
How does the hyperspec state that? Is it the line "Exceptional
situations: None"?
Seems like LispWorks and Allegro are non-conformant, while OpenMCL
behaves like CMUCL;
CL-USER 18 > (progn (format t "~A ~A" (lisp-implementation-type)
(lisp-implementation-version))
(subtypep 'not-a-type t))
LispWorks Personal Edition 4.3.7
Error: NOT-A-TYPE is an illegal type specifier.
1 (abort) Return to level 0.
2 Return to top loop level 0.
Type :b for backtrace, :c <option number> to proceed, or :? for
other options
CL-USER 19 : 1 >
CL-USER(1): (progn (format t "~A ~A" (lisp-implementation-type)
(lisp-implementation-version))
(subtypep 'not-a-type t))
International Allegro CL Enterprise Edition 6.2 [Linux (x86)] (Nov 8,
2003 22:45)
Error: NOT-A-TYPE is not a valid type specifier
[condition type: SIMPLE-ERROR]
Restart actions (select using :continue):
0: Return to Top Level (an "abort" restart).
1: Abort entirely from this process.
[1] CL-USER(2):
? (progn (format t "~A ~A" (lisp-implementation-type)
(lisp-implementation-version))
(subtypep 'not-a-type t))
OpenMCL Version (Beta: Darwin) 0.14.3
T
T
?
--
chr
Cellphone: +4797185074
