From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Andy |
|
| Line 1: |
Line 1: |
| − | = Defining Translations Using The Theory Plug-in =
| |
| − | The theory plug-in is used to add mathematical extensions to Rodin. The theories are created, and deployed, and can then be used in any models in the workspace. When dealing with implementation level models, such as in Tasking Event-B, we need to consider how to translate newly added types and operators into code. We have augmented the theory interface with a Translation Rules section. This enables a user to define translation rules that map Event-B formulas to code.
| |
| − | == Translation Rules==
| |
| − | <div id="fig:Translation Rules">
| |
| − | <br/>
| |
| − | [[Image:TheoryCGRules.png|center||caption text]]
| |
| − | <center>'''Figure 1''': Translation Rules</center>
| |
| − | <br/>
| |
| − | </div>
| |
| | | | |
| − | Figure 1 shows the interface, and some translations rules of the mapping to Ada.
| |
| − |
| |
| − | The theory is given a name, and may import some other theories. Type parameters can be added, and we use them here to type the meta-variables. The meta-variable ''a'' is restricted to be an integer type, but meta-variable ''c'' can be any type.
| |
| − |
| |
| − | The translator rules are templates used for pattern matching. The meta-variables are defined and typed, and used in the rules. Event-B expressions and predicates are defined on the left hand side of the rule, and the code to be output (as text) appears on the right hand side of the matching rule.
| |
| − |
| |
| − | == Type Rules ==
| |
| − |
| |
| − | The type rules section, shown in Figure 1, is where the relationship is defined, between Event-B types and the type system of the implementation.
| |
| − |
| |
| − | = Adding new Types =
| |
| − | In the following example we wish to add a new type to Event-B, and then define its translation to code.
| |
Latest revision as of 20:50, 30 April 2020
