anchor.diff:    "Pretty print the name of a method specializer"
     (cond ((classp spec)
            (princ-to-string (class-name spec)))
  -        ((eql-specializer-p spec)
  -         (format nil "(EQL '~A)" (eql-specializer-object spec)))
  +        ((typep spec 'clim-mop:eql-specializer)
  +         (format nil "(EQL '~A)" (clim-mop:eql-specializer-object spec)))
           (t (princ-to-string spec))))
   
   (defun maybe-find-gf (name)
  
positive.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
  ;;;     method combination and qualifiers with substantially less work.
  ;;;   * Change focus behavior of McCLIM text entry gadget
  ;;;   * Implement focus-aware cursor shapes in McCLIM and/or Goatee
  ;;;     (actually I did this ages ago, but let it rot away on my disk..)
  
negative.code:          collect (remove-duplicates (mapcar (lambda (specs) (nth index specs))
                                              specializers)))))
  
  ;;; FIXME: why is this necessary?  I'm pretty sure the #+CMU clause
  ;;; here has been superseded by events for quite a while now.  (Should
  ;;; clim-mop:class not cater for these implementation differences?)
  (defun classp (x)
    (or (typep x 'cl:class)
        #+CMU (typep x 'pcl::class)
        #+scl (typep x 'clos::std-class)))
  
  (defun compute-applicable-methods-from-specializers (gf specializers)
    (clim-mop:compute-applicable-methods gf
       (mapcar (lambda (spec)
                 (cond ((typep spec 'clim-mop:eql-specializer)
                        (clim-mop:eql-specializer-object spec))
                       ((classp spec)
                        (clim-mop:class-prototype spec))
                       (t (error "Can't compute effective methods, specializer ~A is not understood." spec))))
  