Difference between revisions of "ECMA"
Jump to navigation
Jump to search
(Assigners are implemented) |
(using interwiki links) |
||
Line 11: | Line 11: | ||
==These features are planned:== |
==These features are planned:== |
||
− | * [ |
+ | * [[issue:81|generic inheritance]] |
− | * [ |
+ | * [[issue:80|generic creation]] |
− | * [ |
+ | * [[issue:79|conversions]] - maybe with a slightly stricter interpretation |
− | * [ |
+ | * [[issue:61|named TUPLE elements]] |
− | * [ |
+ | * [[issue:83|void-safety]] (Liberty implementation will probably differ from ECMA) |
− | * [ |
+ | * [[issue:90|small syntax changes]] - the old syntax will be kept for compatibility for quite some time. |
==These ECMA features are not planned in Liberty:== |
==These ECMA features are not planned in Liberty:== |
Revision as of 19:29, 29 April 2013
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
These ECMA features are already implemented:
- Non-conforming inheritance (although the notation is different)
These ECMA features are already implemented with small deviations:
- Non-conforming inheritance (insert instead of inherit {NONE}) see Typing policy
- Assigners with the following deviations:
- VFAC is not enforced (let the standard rules of the replacing procedure call play instead)
- assigners are inherited with proper renames (ECMA does not explicit the rules in either way)
These features are planned:
- generic inheritance
- generic creation
- conversions - maybe with a slightly stricter interpretation
- named TUPLE elements
- void-safety (Liberty implementation will probably differ from ECMA)
- small syntax changes - the old syntax will be kept for compatibility for quite some time.
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 (planned)
Not yet decided:
- Bracket indexing
See also Compatibility.