ECMA

In ECMA-367 the ECMA committee TC39-TG4 defines an Eiffel standard. Liberty is not committed to fully implement this standard, but there will be much more of the improvements as in SmartEiffel. 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 complicates the language to comply to widespread programming conventions will be evaluated case-by-case.

LibertyEiffel 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:

• generic inheritance
• conversions - maybe with a slightly stricter interpretation
• named TUPLE elements
• void-safety (Liberty implementation will probably differ from ECMA)
• attached vs detached
• across

These ECMA features are not planned in Liberty:

• No-variant agent arguments.

These features are not in ECMA but implemented in Liberty:

• inline agents are closures
• explicit agent conformance rules (see this JOT paper)

Not yet decided:

• TYPE[G] and explicit conversion

See also Compatibility.