Hi,
SBCL pays careful attention to the distinction between a STYLE-WARNING
(a condition strong enough to warrant returning from COMPILE-FILE with
WARNINGSP set) and a compiler note (generally an optimization note,
but sometimes a code deletion note or something similar), which aren't
counted as warnings.
Attached is a patch to implement this. I know cmucl doesn't have this
distinction; I'm unsure as to whether OpenMCL does, so I've just
implemented it for SBCL; the behaviour of other lisps should be
unchanged.
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)
Helmut Eller <heller(a)common-lisp.net> writes:
> +(defun read-next-form ()
> + (handler-case
> + (let* ((length (logior (ash (read-byte *emacs-io*) 16)
> + (ash (read-byte *emacs-io*) 8)
> + (read-byte *emacs-io*)))
> + (string (make-string length)))
> + (sys:read-n-bytes *emacs-io* string 0 length)
> + (read-form string))
> + (condition (c)
> + (throw 'serve-request-catcher c))))
OK, so what is the problem with CMUCL that means it can't use
read-sequence here? I know it used to be broken (did partial reads)
but I thought that was fixed ages ago. Can we not report this as a
bug to the cmucl developers?
Thanks for cleaning up my other mess. Now I have to look through your
structure stuff and who-calls, see what I can steal for sbcl :-)
-dan
--
http://web.metacircles.com/cirCLe_CD - Free Software Lisp/Linux distro
