One alternative method may be to put my custom exception handler in a macro and try to catch the undefined variables during expansion... I am presuming expansion happens at the same time bindings are checked/determined, so I can get a handle on any exceptions in time...
On Sun, Jun 14, 2009 at 12:21 PM, Ramana Kumar<[email protected]> wrote: >> Maybe I don't understand the problem you're trying to solve and why you >> need all the heavy-weight machinery that you're using. > > Yeah I wasn't clear that the issue here is handling undefined > variables. If I didn't worry about skipping expressions with undefined > variables, I could just (import (test-library)) at the top of the > script and let evaluation take its normal course. At present I am not > importing test-library into the testing script, rather I am using > test-library as an argument to eval which is called in the testing > script. >
