diff conditions.lisp @ 2:8fbbb0f14f3c

Factor out conditions from classes.lisp into a new file: conditions.lisp.

darcs-hash:20061016160736-aa3d6-2ad7d468ec2a423825440a6f69cc3e80a4e543fb.gz

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/conditions.lisp	Mon Oct 16 17:07:36 2006 +0100
@@ -0,0 +1,32 @@
+;; Some conditions we might want to be able to signal
+
+(define-condition undefined-action (condition)
+  ;; This condition would apply to an attempt to perform a meaningless
+  ;; operation on an object. This may, initially, include things that
+  ;; are a pain to implement but should really be used when it's
+  ;; genuinely unclear what an operation means in the given
+  ;; context. In such cases, a condition handler might be the best
+  ;; approach anyway.
+  ((operation :initarg :operation
+	      :reader undefined-action-operation)
+   (datatype :initarg :datatype
+	     :reader undefined-action-datatype))
+  (:report (lambda (condition stream)
+	     (format stream "The consequence of performing ~A on and object of type ~A is undefined"
+		     (undefined-action-operation condition)
+		     (undefined-action-datatype condition)))
+
+(define-condition insufficient-information (condition)
+  ;; It should be possible to construct genuinely minimal musical
+  ;; structures. When the information in these is insufficient to
+  ;; answer a query, this condition should be raised.
+  ((operation :initarg :operation
+	      :reader insufficient-information-operation)
+   (datatype :initarg :datatype
+	     :reader insufficient-information-datatype))
+  (:report (lambda (condition stream)
+	     (format stream "The ~A object does not contain enough information to perform ~A"
+		     (insufficient-information-datatype condition)
+		     (insufficient-information-operation condition)))
+
+