On Sep 19, 2011, at 1:47 PM, Jeremy Kun wrote: > Not sure if this is a bug, but it doesn't match the documentation here. It > says test/exn only succeeds when the error is explicitly raised by the user, > but I try something as simple as: > > "file1.rkt" > (provide foo) > (define (foo) (error "hello")) > > "file2.rkt" > (require plai "file1.rkt") > (test/exn (foo) "hello") > > and the test fails with "no expected value". I can even replace "hello" with > a call to error, and see that that argument is never evaluated. So by > user-written code, I'm assuming they mean code contained in the same module. > Or am I missing something fundamental about Racket's idea of "user-written > code"?
Just a quick look, but it looks like you're failing to thunk the arguments to test/exn, so it never even gets control. John
smime.p7s
Description: S/MIME cryptographic signature
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users

