Joshua N Pritikin <vishnu@...> writes:
> When I load/compile KM (http://www.cs.utexas.edu/users/mfkb/RKF/km.html),
> I get lots of problems with sb-ext:defconstant-uneql. I'm not a lisp
> wizard yet. How do I temporarily disable this warning?
The short answer is to do something like this: where previously you
have been instructed to do
(load "km.lisp")
or
(compile-file "km.lisp"),
you'll need to do
(handler-bind ((sb-ext:defconstant-uneql #'abort))
(compile-file "km.lisp")) ; or (load "km") or whatever.
I hope that should get you past this particular hurdle, anyway.
(Background information: the problem that you're seeing is a result of
dealing with structured constant data in a language which also
provides guarantees on object identity. In less high-falutin'
language, the problem is similar to the difference between a pointer
to a read-only object and a read-only pointer to an object).
Cheers,
Christophe
--
http://www-jcsu.jesus.cam.ac.uk/~csr21/ +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%") (pprint #36rJesusCollegeCambridge)
|