-
Notifications
You must be signed in to change notification settings - Fork 25
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
Type checker: missing exit checks #14
Comments
|
Still present in 2.0.0b2 |
|
|
|
|
Still in 2.0 |
Please add test case! |
Here you go...
|
This is now much improved in VDMJ and the example above is certainly reporting problems correctly:
Applying the changes to the Overture visitor framework next... |
Now fixed in Overture on ncb/development. |
Added some extra changes that allow expressions to be searched for exit clauses (via their apply calls, which may be operations that raise exceptions). |
The type checking of statements which handle exceptions (eg. trap) looks for whether the body of the specification covered can in fact throw exceptions, raising an error if not. This search process is limited in VDMJ. In particular, it cannot cross an operation call, assuming that all operations can raise exceptions. This leads to false negatives - not reporting a TC error, when it should.
The text was updated successfully, but these errors were encountered: