ADVANCE D3.2 Language extension

Overview

Mathematical extensions have been co-developed by Systerel (for the Core Rodin Platform) and Southampton (for the Theory plug-in). The main purpose of this new feature was to provide the Rodin user with a way to extend the standard Event-B mathematical language by supporting user-defined operators, basic predicates and algebraic types. Along with these additional notations, the user can also define new proof rules (proof extensions).

The Theory plug-in provides, among other things, a user-friendly mechanism to extend the Event-B mathematical language as well as the prover. A theory is the dedicated component used to hold mathematical extensions (datatypes, operators with direct definitions, operators with recursive definitions and operators with axiomatic definitions), and proof extensions (polymorphic theorems, rewrite and inference rules). Theories are developed in the workspace (akin to models), and are subject to static checking and proof obligation generation. Proof obligations generated from theories ensure any contributed extensions do not compromise the soundness of the existing infrastructure for modelling and proof. In essence, the Theory plug-in provides a systematic platform for defining, validating and using extensions while exploiting the benefits brought by proof obligations.

Motivations / Decisions

Supporting mathematical and proof extensions has been a longing for the Event-B community for considerable time. Serious considerations have been made to ensure any support ensures: 1) ease of use, and 2) soundness preservation. Earlier versions of the Theory plug-in provided support for rewrite rules where soundness is preserved by means of proof obligations. The Theory plug-in became a natural candidate to provide support for mathematical and proof extensions. The use of proof obligations goes a long way in preserving the soundness of the underlying Event-B formalism.

In the past 9 months, the development of the Theory plug-in resulted in the following additions:

• Support for polymorphic theorems in proofs: theorems can be used to ensure the operator and datatype definitions capture the intended understanding by the theory developer. However, requests have been made to ensure that theorems are accessible for proofs. It was decided to provide a user interface-based wizard for instantiating the type parameters in order to 'localise' the theorem based on the current sequent.
• Added support of axiomatic definitions: as of version 1.3.2 of the Theory plug-in, only direct and recursive definitions for operators are possible. Requests have been made to add support for axiomatic operator definitions, which can open the door for sophisticated type definitions, e.g., the definition of REALS as an ordered ring with addition and multiplication.
• From version 2.6 of Rodin, the Theory plug-in will ship as part of the core distribution. This particular decision was made given the maturity of the plug-in and its potential usefulness.

Available Documentation

Pre-studies (states of the art, proposals, discussions):

• Proposals for Mathematical Extensions for Event-B.
• Mathematical Extension in Event-B through the Rodin Theory Component.
• Generic Parser's Design Alternatives.

Technical details (specifications):

• Mathematical_Extensions wiki page.
• Constrained Dynamic Lexer wiki page.
• Constrained Dynamic Parser wiki page.
• Theory plug-in wiki page.

User's guides:

• Theory Plug-in User Manual.

Planning

The Theory plug-in became part of the core distribution of Rodin since version 2.6.