<div dir="ltr">Realize that the book is 5 years behind the latest tools, so you'll find some inconsistencies and weirdness.<br><div class="gmail_quote"><div dir="ltr"><br>You can check that errors are thrown by using the (check-error ...) version of test cases. Here's a working example:<br> <br>(define (blah x)<br>  (error 'blah "undefined"))<br><br>(check-error (blah 5) "blah: undefined")<br><font color="#888888"><br>Todd</font><div><div></div><div class="Wj3C7c"><br><br><div class="gmail_quote"> On Fri, Sep 12, 2008 at 8:38 PM, Grant Rettke <span dir="ltr"><<a href="mailto:grettke@acm.org" target="_blank">grettke@acm.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br> <br> Was sub-chapter 7.5 a point of contention?<br> <br> I like contracts, but it doesn't feel like it fits.<br> <br> Evidence:<br> * Less than 3 pages<br> * We are encouraged to raise errors, but we haven't got a unit-testing<br> tool to actually check if they were raised.<br> <br> I argued that the goal is to show that we grok how to provide checked<br> versions of our functions to clients, so function documentation and<br> unit tests aren't required here.<br> <br> Best wishes,<br> <br> Grant<br> _________________________________________________<br>  For list-related administrative tasks:<br>  <a href="http://list.cs.brown.edu/mailman/listinfo/plt-scheme" target="_blank">http://list.cs.brown.edu/mailman/listinfo/plt-scheme</a><br> </blockquote></div><br></div></div></div> </div><br></div>