From Liberty Eiffel Wiki
Revision as of 15:02, 9 September 2018 by Hzwakenberg (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

In ECMA-367 the ECMA committee TC39-TG4 defines an Eiffel standard. Liberty is not committed to fully implement this standard, but it will adopt many more of the improvements than its predecessor did at the time. Liberty will implement those parts of ECMA that match the effective, efficient and simple design of previous versions of Eiffel. The parts requiring an extensive run-time model will not be currently implemented; those that needlessly complicate the language to comply to widespread programming conventions will be evaluated case-by-case.

Liberty Eiffel offers these ECMA features already:

  • attribute keyword may be used to define an attribute including self-initialization with contracts checking.

With small deviations:

  • Non-conforming inheritance (but using insert instead of inherit {NONE}); see Typing policy
  • Assigners with the following deviations:
    • VFAC (ECMA §8.5.22) is not enforced (let the standard rules of the replacing procedure call play instead)
    • assigners are inherited with proper renames (ECMA does not explicitly specify the rules either way)
  • Cosmetic syntax changes:
    • is is now optional
    • alias is implemented, including alias "[]"
    • note replaces indexing and can be placed at the start and end of a class, and at the start of a feature
    • create replaces creation
  • generic creation

These ISE features are also implemented:

These features are not (yet) in the ECMA standard:

  • the newer alias "()"
  • its companion implicit tuples
  • if-then-else expressions

These features are planned:

These ECMA features are not planned in Liberty:

  • No-variant agent arguments.

These features are not in ECMA but implemented in Liberty:

Not yet decided:

  • TYPE[G] and explicit conversion
  • postcondition of is_equal: same_type: Result implies same_type(other)
    • this essentially forbids any equal objects with different types and is inconsistent to the current implementation in Liberty. It has some nice background (e. g. symmetry is not easy to guarantee without that), but we also do not want to brake existing code

See also Compatibility.