anchor.diff:                      (cond
                         ((eql a (find-class t)) t)
                         ((eql b (find-class t)) nil)
  -                      (t (string< (class-name a)
  -                                  (class-name b)))))))
  +                      ((and (classp a)
  +                            (classp b))
  +                       (string< (class-name a)
  +                                (class-name b)))
  +                      ((and (eql-specializer-p a)
  +                            (not (eql-specializer-p b)))
  +                       nil)
  +                      ((and (not (eql-specializer-p a))
  +                            (eql-specializer-p b))
  +                       t)
  +                      ((and (eql-specializer-p a)
  +                            (eql-specializer-p b))
  +                       (string<
  +                        (princ-to-string (eql-specializer-object a))
  +                        (princ-to-string (eql-specializer-object b))))
  +                      (t (warn "Received specializer of unknown type")
  +                         nil) ))))
             (compute-gf-specializers gf)))
   
   (defun simple-generic-function-lambda-list (gf)
  
positive.code: ;;; --------------------------------------------------------------------
  
  ;;; This is an example of how to write a CLIM application with a
  ;;; "normal" GUI. McCLIM can do more than just command lines..
  
  ;;; Running the method-browser:
  ;;;   (clim-demo::run-test 'clim-demo::method-browser)
  
negative.code: ;;;   * Portable MOP provided by CLIM-MOP package
  
  ;;; TODO:
  ;;;   * EQL specializers on implementations other than SBCL/CMUCL
  ;;;   * Nicer, more clever display of methods than simply listing them in a row.
  ;;;     To do this right really involes some nonportable fun and a codewalker.
  ;;;     You could probably write something that just understood the standard
  