Mathematical Extensions: Difference between revisions

From Event-B
Jump to navigationJump to search
imported>Laurent
mNo edit summary
imported>Nicolas
mNo edit summary
Line 11: Line 11:
# Extensions of the library of theorems for predicates and operators.
# Extensions of the library of theorems for predicates and operators.
# Extensions of the Set Theory itself through the definition of algebraic types such as  lists or ordered trees using new set constructors.
# Extensions of the Set Theory itself through the definition of algebraic types such as  lists or ordered trees using new set constructors.
== Towards a generic AST ==
The following AST parts are to become generic, or at least parameterised:
* Lexer
* Parser
* Nodes ( Formula class hierarchy ): parameters needed for:
** Type Solve (how to synthesize the type)
** Type Check (how to verify constraints on children types)
** WD
** PrettyPrint (tag image + notation (prefix, infix, postfix))
* Formula Factory
== Impact on other tools ==
Impacted plug-ins (use a factory to build formulæ):
* org.eventb.core
* org.eventb.core.seqprover
* org.eventb.pp
* org.eventb.pptrans
* org.eventb.ui


[[Category:Design proposal]]
[[Category:Design proposal]]

Revision as of 17:39, 6 January 2010

Currently the operators and basic predicates of the Event-B mathematical language supported by Rodin are fixed. We propose to extend Rodin to support user-defined data types and associated operators including inductive data types. Users will be able to define operators of polymorphic type as well as parameterised predicate definitions.

Details of the proposal may be found in this report : Proposals for Mathematical Extensions for Event-B

The proposal consists of considering three kinds of extension:

  1. Extensions of set-theoretic expressions or predicates: example extensions of this kind consist of adding the transitive closure of relations or various ordered relations.
  2. Extensions of the library of theorems for predicates and operators.
  3. Extensions of the Set Theory itself through the definition of algebraic types such as lists or ordered trees using new set constructors.


Towards a generic AST

The following AST parts are to become generic, or at least parameterised:

  • Lexer
  • Parser
  • Nodes ( Formula class hierarchy ): parameters needed for:
    • Type Solve (how to synthesize the type)
    • Type Check (how to verify constraints on children types)
    • WD
    • PrettyPrint (tag image + notation (prefix, infix, postfix))
  • Formula Factory

Impact on other tools

Impacted plug-ins (use a factory to build formulæ):

  • org.eventb.core
  • org.eventb.core.seqprover
  • org.eventb.pp
  • org.eventb.pptrans
  • org.eventb.ui