view base/conditions.lisp @ 193:c18f795f4463

rollback the amuse.asd generics/classes dependency fix

Ignore-this: be4e0351d31f24f5348cc8dc434477dc

Fix properly this time by moving the specialized get-constituents method from generics to methods.

rolling back:

Wed Jan 23 15:55:34 GMT 2008  Jamie Forth <[e-mail]>
  * Fixed amuse.asd dependency - generics depends on classes.

    M ./amuse.asd -2 +2

darcs-hash:20090524164116-16a00-2b561eab1a5829a251eb5e9b40357945af13e6a6.gz

(cl:in-package #:amuse) 

;; 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 an 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)))))