<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 19 Jan 2010, at 8:23:22, <a href="mailto:plt-scheme-request@list.cs.brown.edu">plt-scheme-request@list.cs.brown.edu</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Times; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Message: 1<br>Date: Tue, 19 Jan 2010 11:40:28 -0800<br>From: John Clements <<a href="mailto:clements@brinckerhoff.org">clements@brinckerhoff.org</a>><br>Subject: [plt-scheme] check-expect exceptionalism bites again.<br>To: PLT-Scheme Mailing List <<a href="mailto:plt-scheme@list.cs.brown.edu">plt-scheme@list.cs.brown.edu</a>><br>Message-ID: <<a href="mailto:F54E93D3-1F6D-4262-BAD7-160A45705EA1@brinckerhoff.org">F54E93D3-1F6D-4262-BAD7-160A45705EA1@brinckerhoff.org</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>I'm putting together a simple teach-yourself-scheme website--I'll show more when I've got more to show--and the goofy evaluation rules for check-expect have bitten me again. Specifically, sending (check-expect 3 4) to an evaluator created with the sandbox evaluator produces void, and presumably the check-expect is going onto a pile to get evaluated "later". Grr!<br><br>Seems to me like it would be easier just to tell everyone to put their darn test cases as the end of the program.<br><br>Yes, in some sense this is yet another "top level is broken" comment.<br><br>I can see two straightforward solutions that keep the world the way it is:<br>1) create a "dont-delay-test-cases" parameter that--when set--would cause test cases to expand into call-right-now test cases<br>2) create a "trigger-test-case-queue" function that would tell a sandbox evaluator to go ahead and run its test cases.<br><br>Either of these sound good / simple? Is there a simpler solution?<br></span></blockquote></div><br><div>There is (outside of the teaching languages) a function to trigger running the tests, provided by test-engine/scheme-tests -- (test); I could add a parameter to run the tests as soon as they're seen, if there's sufficient desire. </div><div><br></div><div>The results are unlikely to be displayed in a sandbox environment though, for which the test library needs to provide a better interface.</div><div><br></div><div>-Kathy</div></body></html>