The Overture Tool release 2.5.4

Overture v2.5.4 - Release Notes - 10 November 2017

What's New?

This release contains several bug fixes and enhancements for Overture's core features (e.g. type-checker and interpreter), and increased coverage of constructs that can be code-generated to Java (see details below).

Reporting Problems and Troubleshooting

Please report bugs, problems, and other issues with the tool at https://github.com/overturetool/overture/issues.

If you encounter a problem with the Overture IDE itself, please contact the Overture project and we will try to help. You can contact us at [email protected], or use StackOverflow — we monitor for questions using the vdm, vdm++, or vdmrt tags.

If you encounter a problem with a VDM specification, please try to make a small example that illustrates the problem before you contact us. If you are sure the bug is not already known in the GitHub issues list, you can create a new bug report.

Other Resources and Links

• Overture Community site
• VDM-10 Language Manual
• VDM Tutorials
• VDM Examples
• Wikipedia on VDM
• Overture Developers Wiki on GitHub
• The Old Overture Wiki for developers

Bugfixes

Please note that the interactive list is at https://github.com/overturetool/overture/milestone/36

• #650 closed - Java code-generator does not handle the nondeterministic statement correctly
• #649 closed - ** operator type errors have wrong location information
• #648 closed - Extend Java code-generation support for maps
• #647 closed - Interpreter fails to find object member
• #646 closed - File AlarmInitUML.uml
• #645 closed - Add support for code-generation of the iota expression
• #643 closed - Mu expressions can miss type checking errors
• #642 closed - Generating PDF with the modelOnly preference does not drop non-model text
• #641 closed - When pretty printing with the option where model only is switched off one shall not generate \section{ClassName}