Difference between revisions of "ECMA"
Jump to navigation
Jump to search
(Created page with "In [http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-367.pdf ECMA-367] the ECMA committee TC39-TG4 defines an Eiffel standard. Liberty is not committed to fully …") |
m (→Not yet decided:: fixed link) |
||
| Line 25: | Line 25: | ||
* Bracket indexing |
* Bracket indexing |
||
| − | See also [Combatibility]. |
+ | See also [[Combatibility]]. |
Revision as of 23:18, 5 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})
These features are planned:
- generic inheritance
- generic creation
- Conversions - maybe with a slightly stricter interpretation
- named TUPLE elements
- attribute setters
- void-safety (Liberty implementation will probably differ from ECMA)
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:
- Feature aliases
- Bracket indexing
See also Combatibility.