Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make default behavior to stop all analysis on first exception thrown #79

Closed
jafingerhut opened this issue Jul 23, 2014 · 1 comment
Closed

Comments

@jafingerhut
Copy link
Collaborator

The current behavior is to stop analyzing a single file if an exception is thrown, but to go on and try to analyze other namespaces. However, when an exception is thrown on one namespace, no further analysis and eval is done for any later forms in the file. Thus if there are Vars defined later in that file with the first exception, it can cause undefined Var exceptions during analysis of later namespaces that assume that Var is defined, which is misleading.

It still might be useful for my own development testing to have an option to operate as it currently does, because then output from one crucible run to the next might be more consistent.

@jafingerhut
Copy link
Collaborator Author

This enhancement was first released as part of Eastwood version 0.1.5

jfacorro pushed a commit to jfacorro/eastwood that referenced this issue Nov 6, 2014
Also added command line option :continue-on-exception that when true
will behave as before, possibly with spurious exceptions on later
namespaces.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant