X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=tests%2Finterface.pure.lisp;h=c84cc6343379a6ceed282a839a1e3866f190b5a8;hb=e92a2f8844d9125e76a4b96dc27b56632bfd85b6;hp=4ad2ffa86e77c6bca2c7b48066f2c290fec1693d;hpb=4eb1a6d3ad2b7dcc19ac0ec979a1eb1eb049659a;p=sbcl.git

diff --git a/tests/interface.pure.lisp b/tests/interface.pure.lisp
index 4ad2ffa..c84cc63 100644
--- a/tests/interface.pure.lisp
+++ b/tests/interface.pure.lisp
@@ -15,56 +15,6 @@
 
 ;;;; properties of symbols, e.g. presence of doc strings for public symbols
 
-;;; Check for fbound external symbols in public packages that have no
-;;; argument list information. (This used to be possible when we got
-;;; carried away with byte compilation, since the byte compiler can't
-;;; record argument list information. Now that there's no byte
-;;; compiler, that can't happen, but it still shouldn't hurt to check
-;;; in case the argument information goes astray some other way.)
-(defvar *public-package-names*
-  '("SB-ALIEN" "SB-C-CALL" "SB-DEBUG" "SB-EXT" "SB-GRAY" "SB-MP"
-    "SB-PROFILE" "SB-PCL" "COMMON-LISP"))
-(defun has-arglist-info-p (fun)
-  (declare (type function fun))
-  ;; The Lisp-level type FUNCTION can conceal a multitude of sins..
-  (case (sb-kernel:widetag-of fun)
-    ((#.sb-vm:simple-fun-header-widetag #.sb-vm:closure-fun-header-widetag)
-      (sb-kernel:%simple-fun-arglist fun))
-    (#.sb-vm:closure-header-widetag (has-arglist-info-p
-				     (sb-kernel:%closure-fun fun)))
-    ;; In code/describe.lisp, ll. 227 (%describe-function), we use a scheme
-    ;; like above, and it seems to work. -- MNA 2001-06-12
-    ;;
-    ;; (There might be other cases with arglist info also.
-    ;; SIMPLE-FUN-HEADER-WIDETAG and CLOSURE-HEADER-WIDETAG just
-    ;; happen to be the two case that I had my nose rubbed in when
-    ;; debugging a GC problem caused by applying %SIMPLE-FUN-ARGLIST to
-    ;; a closure. -- WHN 2001-06-05)
-    (t nil)))
-(defun check-ext-symbols-arglist (package)
-  (format t "~% looking at package: ~A" package)
-  (do-external-symbols (ext-sym package)
-    (when (fboundp ext-sym)
-      (let ((fun (symbol-function ext-sym)))
-	(cond ((macro-function ext-sym)
-	       ;; FIXME: Macro functions should have their argument list
-	       ;; information checked separately. Just feeding them into
-	       ;; the ordinary-function logic below doesn't work right,
-	       ;; though, and I haven't figured out what does work
-	       ;; right. For now we just punt.
-	       (values))
-	      ((typep fun 'generic-function)
-                (sb-pcl::generic-function-pretty-arglist fun))
-	      (t
-	       (let ((fun (symbol-function ext-sym)))
-		 (unless (has-arglist-info-p fun)
-		   (error "Function ~A has no arg-list information available."
-			  ext-sym)))))))))
-(dolist (public-package *public-package-names*)
-  (when (find-package public-package)
-    (check-ext-symbols-arglist public-package)))
-(terpri)
-
 ;;; FIXME: It would probably be good to require here that every
 ;;; external symbol either has a doc string or has some good excuse
 ;;; (like being an accessor for a structure which has a doc string).
@@ -77,3 +27,31 @@
 (assert (< 0
 	   (length (apropos-list "PRINT" :cl))
 	   (length (apropos-list "PRINT"))))
+;;; Further, it should correctly deal with the external-only flag (bug
+;;; reported by cliini on #lisp IRC 2003-05-30, fixed in sbcl-0.8.0.1x
+;;; by CSR)
+(assert (= (length (apropos-list "" "CL"))
+	   (length (apropos-list "" "CL" t))))
+(assert (< 0
+	   (length (apropos-list "" "SB-VM" t))
+	   (length (apropos-list "" "SB-VM"))))
+
+;;; DESCRIBE shouldn't fail on rank-0 arrays (bug reported and fixed
+;;; by Lutz Euler sbcl-devel 2002-12-03)
+(describe #0a0)
+(describe #(1 2 3))
+(describe #2a((1 2) (3 4)))
+
+;;; TYPEP, SUBTYPEP, UPGRADED-ARRAY-ELEMENT-TYPE and
+;;; UPGRADED-COMPLEX-PART-TYPE should be able to deal with NIL as an
+;;; environment argument
+(typep 1 'fixnum nil)
+(subtypep 'fixnum 'integer nil)
+(upgraded-array-element-type '(mod 5) nil)
+(upgraded-complex-part-type '(single-float 0.0 1.0) nil)
+
+;;; We should have documentation for our extension package:
+(assert (documentation (find-package "SB-EXT") t))
+
+;;; DECLARE should not be a special operator
+(assert (not (special-operator-p 'declare)))