Pascal J.Bourguignon <pjb@...> writes:
> (DEFINE-CONDITION DATA-ERROR (ERROR)
> :DOCUMENTATION "The variable name that contains a bad value.")
> (:DOCUMENTATION "A condition occuring when bad input data is detected.")
This causes no problems with current CVS, or indeed the latest
released version of SBCL.
> (I'd have tested it with the CVS head, but the test suite gives the
> following error on the current CVS head:
> Top 10 dynamic instance types:
> unhandled condition (of type SB-INT:BUG):
> failed AVER: "(SAP= CURRENT END)"
I don't see this, but here it's possible that your CVS HEAD isn't the
same as my CVS HEAD, thanks to SourceForge's slightly odd way of
managing access to source. I would guess that this version is one of
the ones affected by the GCish problems of a week or so ago.
In general, though, it's somewhat hard to guess what the problem is
(in either of your two bug reports) without even the crutch of a
version number. (lisp-implementation-version) is intended to provide
a sufficiently fine-grained distinction that developers, or indeed
anyone with access to the CVS history, can work out what changes could
have caused the general problems observed; without it, one has to fall
back on deduction and ESP in equal measure to divine what the issues
involved are -- and these are, sadly, more fallible than knowledge.
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)