![](https://secure.gravatar.com/avatar/8426fd1e01564a36934e5c99ab49cb54.jpg?s=120&d=mm&r=g)
Dear Ville, Enclosed are the samples you requested. The file error.lisp can produce either error depending on witch code you uncomment. Obviously, the errors are intended. The error message is what is in question. To use, load clos-utils.lisp first and then error.lisp. I hope this is helpful. Thanks for your help. Blake McBride On Sun, Jan 23, 2011 at 12:41 PM, Ville Voutilainen <ville.voutilainen@gmail.com> wrote:
On 23 January 2011 20:15, Ville Voutilainen <ville.voutilainen@gmail.com> wrote:
return null. That fixes the (time) example Blake posted, and does the right thing for type-errors that used to print unboundValue. I'll go through the rest of Blake's reports, see that the others are fixed and will commit the patch after that. Thanks for the reports, fixing this soon.
Blake, do you have simple snippets that cause the slot/method printouts? I was unable to cause such printouts with some simple slot/method cases I've tried, so I need some tests to check whether I've fixed it all.