X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fcondition.lisp;h=d6cfa9d1c11bb645fc917f07edc081caab6596c2;hb=da54f0f75754190f30f8585ff05bebd254aa4e40;hp=d7517ae48f7186473faefab7449e2d08c87757c3;hpb=74a48d09e08aead6f67204878bdf9be4f448e1e8;p=sbcl.git

diff --git a/src/code/condition.lisp b/src/code/condition.lisp
index d7517ae..d6cfa9d 100644
--- a/src/code/condition.lisp
+++ b/src/code/condition.lisp
@@ -1,8 +1,6 @@
 ;;;; stuff originally from CMU CL's error.lisp which can or should
 ;;;; come late (mostly related to the CONDITION class itself)
 ;;;;
-;;;; FIXME: should perhaps be called condition.lisp, or moved into
-;;;; classes.lisp
 
 ;;;; This software is part of the SBCL system. See the README file for
 ;;;; more information.
@@ -499,10 +497,6 @@
 	  (t
 	   (error "unknown option: ~S" (first option)))))
 
-      (when (all-writers)
-	(warn "Condition slot setters probably not allowed in ANSI CL:~%  ~S"
-	      (all-writers)))
-
       `(progn
 	 (eval-when (:compile-toplevel :load-toplevel :execute)
 	   (%compiler-define-condition ',name ',parent-types ',layout))
@@ -588,15 +582,7 @@
   ((pathname :reader file-error-pathname :initarg :pathname))
   (:report
    (lambda (condition stream)
-     (format stream
-	     "~@<error on file ~_~S: ~2I~:_~?~:>"
-	     (file-error-pathname condition)
-	     ;; FIXME: ANSI's FILE-ERROR doesn't have FORMAT-CONTROL and 
-	     ;; FORMAT-ARGUMENTS, and the inheritance here doesn't seem
-	     ;; to give us FORMAT-CONTROL or FORMAT-ARGUMENTS either.
-	     ;; So how does this work?
-	     (serious-condition-format-control condition)
-	     (serious-condition-format-arguments condition)))))
+     (format stream "error on file ~S" (file-error-pathname condition)))))
 
 (define-condition package-error (error)
   ((package :reader package-error-package :initarg :package)))
@@ -618,6 +604,13 @@
 	     "The function ~S is undefined."
 	     (cell-error-name condition)))))
 
+(define-condition special-form-function (undefined-function) ()
+  (:report
+   (lambda (condition stream)
+     (format stream
+	     "Cannot FUNCALL the SYMBOL-FUNCTION of special operator ~S."
+	     (cell-error-name condition)))))
+
 (define-condition arithmetic-error (error)
   ((operation :reader arithmetic-error-operation
 	      :initarg :operation
@@ -703,6 +696,21 @@
 	     "The index ~S is too large."
 	     (type-error-datum condition)))))
 
+;;; Out-of-range &KEY END arguments are similar to, but off by one
+;;; from out-of-range indices into the sequence.
+;;;
+;;; FIXME: Uh, but it isn't used for &KEY END things -- in fact, this
+;;; is only used in one place, in SUBSEQ.  Is it really necessary?  Is
+;;; it here so that we can actually go round seq.lisp decorating all
+;;; the sequence functions with extra checks?  -- CSR, 2002-11-01
+(define-condition end-too-large-error (type-error)
+  ()
+  (:report
+   (lambda (condition stream)
+     (format stream
+	     "The end-of-sequence specifier ~S is too large."
+	     (type-error-datum condition)))))
+
 (define-condition io-timeout (stream-error)
   ((direction :reader io-timeout-direction :initarg :direction))
   (:report
@@ -715,8 +723,7 @@
 
 (define-condition namestring-parse-error (parse-error)
   ((complaint :reader namestring-parse-error-complaint :initarg :complaint)
-   (arguments :reader namestring-parse-error-arguments :initarg :arguments
-	      :initform nil)
+   (args :reader namestring-parse-error-args :initarg :args :initform nil)
    (namestring :reader namestring-parse-error-namestring :initarg :namestring)
    (offset :reader namestring-parse-error-offset :initarg :offset))
   (:report
@@ -724,7 +731,7 @@
      (format stream
 	     "parse error in namestring: ~?~%  ~A~%  ~V@T^"
 	     (namestring-parse-error-complaint condition)
-	     (namestring-parse-error-arguments condition)
+	     (namestring-parse-error-args condition)
 	     (namestring-parse-error-namestring condition)
 	     (namestring-parse-error-offset condition)))))
 
@@ -740,6 +747,80 @@
 	     "unexpected end of file on ~S ~A"
 	     (stream-error-stream condition)
 	     (reader-eof-error-context condition)))))
+
+(define-condition reader-impossible-number-error (reader-error)
+  ((error :reader reader-impossible-number-error-error :initarg :error))
+  (:report
+   (lambda (condition stream)
+     (let ((error-stream (stream-error-stream condition)))
+       (format stream "READER-ERROR ~@[at ~W ~]on ~S:~%~?~%Original error: ~A"
+	       (file-position error-stream) error-stream
+	       (reader-error-format-control condition)
+	       (reader-error-format-arguments condition)
+	       (reader-impossible-number-error-error condition))))))
+
+;;;; special SBCL extension conditions
+
+;;; an error apparently caused by a bug in SBCL itself
+;;;
+;;; Note that we don't make any serious effort to use this condition
+;;; for *all* errors in SBCL itself. E.g. type errors and array
+;;; indexing errors can occur in functions called from SBCL code, and
+;;; will just end up as ordinary TYPE-ERROR or invalid index error,
+;;; because the signalling code has no good way to know that the
+;;; underlying problem is a bug in SBCL. But in the fairly common case
+;;; that the signalling code does know that it's found a bug in SBCL,
+;;; this condition is appropriate, reusing boilerplate and helping
+;;; users to recognize it as an SBCL bug.
+(define-condition bug (simple-error)
+  ()
+  (:report
+   (lambda (condition stream)
+     (format stream
+	     "~@<  ~? ~:@_~?~:>"
+	     (simple-condition-format-control condition)
+	     (simple-condition-format-arguments condition)
+	     "~@<This is probably a bug in SBCL itself. (Alternatively, ~
+              SBCL might have been corrupted by bad user code, e.g. by an ~
+              undefined Lisp operation like ~S, or by stray pointers from ~
+              alien code or from unsafe Lisp code; or there might be a bug ~
+              in the OS or hardware that SBCL is running on.) If it seems to ~
+              be a bug in SBCL itself, the maintainers would like to know ~
+              about it. Bug reports are welcome on the SBCL ~
+              mailing lists, which you can find at ~
+              <http://sbcl.sourceforge.net/>.~:@>"
+	     '((fmakunbound 'compile))))))
+(defun bug (format-control &rest format-arguments)
+  (error 'bug
+	 :format-control format-control
+	 :format-arguments format-arguments))
+
+;;; a condition for use in stubs for operations which aren't supported
+;;; on some platforms
+;;;
+;;; E.g. in sbcl-0.7.0.5, it might be appropriate to do something like
+;;;   #-(or freebsd linux)
+;;;   (defun load-foreign (&rest rest)
+;;;     (error 'unsupported-operator :name 'load-foreign))
+;;;   #+(or freebsd linux)
+;;;   (defun load-foreign ... actual definition ...)
+;;; By signalling a standard condition in this case, we make it
+;;; possible for test code to distinguish between (1) intentionally
+;;; unimplemented and (2) unintentionally just screwed up somehow.
+;;; (Before this condition was defined, test code tried to deal with 
+;;; this by checking for FBOUNDP, but that didn't work reliably. In
+;;; sbcl-0.7.0, a a package screwup left the definition of
+;;; LOAD-FOREIGN in the wrong package, so it was unFBOUNDP even on
+;;; architectures where it was supposed to be supported, and the
+;;; regression tests cheerfully passed because they assumed that
+;;; unFBOUNDPness meant they were running on an system which didn't
+;;; support the extension.)
+(define-condition unsupported-operator (cell-error) ()
+  (:report
+   (lambda (condition stream)
+     (format stream
+	     "unsupported on this platform (OS, CPU, whatever): ~S"
+	     (cell-error-name condition)))))
 
 ;;;; restart definitions