Compatibility - Revision history

Hzwakenberg: lingual correction

2024-07-10T08:06:56Z

lingual correction

← Older revision		Revision as of 10:06, 10 July 2024
Line 29:		Line 29:
	== Differences between the former SmartEiffel and ECMA Eiffel ==		== Differences between the former SmartEiffel and ECMA Eiffel ==

−	The [http://www.ecma-international.org/publications/standards/Ecma-367.htm ECMA Eiffel specification] does not describe any current implementation at the time of writing this (November 2005). Despite being a standard it describes several features that fork away from what always ~~has~~ been called "Eiffel". The following aspects of ECMA Eiffel will not be implemented in SmartEiffel:	+	The [http://www.ecma-international.org/publications/standards/Ecma-367.htm ECMA Eiffel specification] does not describe any current implementation at the time of writing this (November 2005). Despite being a standard it describes several features that fork away from what always had been called "Eiffel". The following aspects of ECMA Eiffel will not be implemented in SmartEiffel:

	* Conversions (implemented in ISE Eiffel)		* Conversions (implemented in ISE Eiffel)

Hzwakenberg: spelling / removed passive voice

2021-12-21T21:37:19Z

spelling / removed passive voice

← Older revision		Revision as of 23:37, 21 December 2021
Line 1:		Line 1:
−	This page is about language compatibility for Liberty Eiffel. ~~You~~ ~~can~~ find ~~here~~ the most important differences between Liberty Eiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most ~~important~~ differences.	+	This page is about language compatibility for Liberty Eiffel. Here you find the most important differences between Liberty Eiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most significant differences.

	See also [[ECMA]].		See also [[ECMA]].
Line 29:		Line 29:
	== Differences between the former SmartEiffel and ECMA Eiffel ==		== Differences between the former SmartEiffel and ECMA Eiffel ==

−	The [http://www.ecma-international.org/publications/standards/Ecma-367.htm ECMA Eiffel specification] does not describe any current implementation at the time of writing this (November 2005). Despite being a standard it describes several features that fork away from what has been ~~always~~ called "Eiffel". The following aspects of ECMA Eiffel will not be implemented in SmartEiffel:	+	The [http://www.ecma-international.org/publications/standards/Ecma-367.htm ECMA Eiffel specification] does not describe any current implementation at the time of writing this (November 2005). Despite being a standard it describes several features that fork away from what always has been called "Eiffel". The following aspects of ECMA Eiffel will not be implemented in SmartEiffel:

	* Conversions (implemented in ISE Eiffel)		* Conversions (implemented in ISE Eiffel)

Dkearns: s/LibertyEiffel/Liberty Eiffel/

2016-06-22T01:52:52Z

s/LibertyEiffel/Liberty Eiffel/

← Older revision		Revision as of 03:52, 22 June 2016
Line 1:		Line 1:
−	This page is about language compatibility for ~~LibertyEiffel~~. You can find here the most important differences between ~~LibertyEiffel~~ and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.	+	This page is about language compatibility for Liberty Eiffel. You can find here the most important differences between Liberty Eiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.

	See also [[ECMA]].		See also [[ECMA]].

−	== Unique peculiarities of ~~LibertyEiffel~~ ==	+	== Unique peculiarities of Liberty Eiffel ==

−	~~LibertyEiffel~~ has some features not implemented by any other implementation:	+	Liberty Eiffel has some features not implemented by any other implementation:

	* Case sensitivity: "abc", "Abc" and "ABC" are different identifiers		* Case sensitivity: "abc", "Abc" and "ABC" are different identifiers
Line 15:		Line 15:
	* New operators for run-time type checking. See [[Dynamic type testing]]		* New operators for run-time type checking. See [[Dynamic type testing]]
	* Removed the danger of automatic boxing (object allocation on assignment of expanded types to reference entities)		* Removed the danger of automatic boxing (object allocation on assignment of expanded types to reference entities)
−	* Lots of additional tools in the library. See [[Table of contents#Library\|The ~~LibertyEiffel~~ general purpose library]]	+	* Lots of additional tools in the library. See [[Table of contents#Library\|The Liberty Eiffel general purpose library]]
	* Notation for [[Manifest storage notation\|manifest collections]]. The old <code><<...>></code> is still supported for simple arrays.		* Notation for [[Manifest storage notation\|manifest collections]]. The old <code><<...>></code> is still supported for simple arrays.
	* Unicode strings manifest notation.		* Unicode strings manifest notation.

Hzwakenberg: /* Unique peculiarities of LibertyEiffel */

2016-03-08T13:20:16Z

Unique peculiarities of LibertyEiffel

← Older revision		Revision as of 15:20, 8 March 2016
Line 18:		Line 18:
	* Notation for [[Manifest storage notation\|manifest collections]]. The old <code><<...>></code> is still supported for simple arrays.		* Notation for [[Manifest storage notation\|manifest collections]]. The old <code><<...>></code> is still supported for simple arrays.
	* Unicode strings manifest notation.		* Unicode strings manifest notation.
−	* Agents look ~~contravarient.~~ ~~But~~ they are not. Believe us. For details and explanations, see [http://www.jot.fm/issues/issue_2004_04/article7 this article].	+	* Agents look contravariant, but they are not. Believe us. For details and explanations, see [http://www.jot.fm/issues/issue_2004_04/article7 this article].

	== Differences between ETL2 and the former SmartEiffel ==		== Differences between ETL2 and the former SmartEiffel ==

Ramack: add link to page ECMA

2014-09-10T19:56:23Z

add link to page ECMA

← Older revision		Revision as of 21:56, 10 September 2014
Line 1:		Line 1:
	This page is about language compatibility for LibertyEiffel. You can find here the most important differences between LibertyEiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.		This page is about language compatibility for LibertyEiffel. You can find here the most important differences between LibertyEiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.
		+
		+	See also [[ECMA]].

	== Unique peculiarities of LibertyEiffel ==		== Unique peculiarities of LibertyEiffel ==

Hzwakenberg: /* Differences between ETL2 and LibertyEiffel */

2014-09-05T19:34:09Z

Differences between ETL2 and LibertyEiffel

← Older revision		Revision as of 21:34, 5 September 2014
Line 18:		Line 18:
	* Agents look contravarient. But they are not. Believe us. For details and explanations, see [http://www.jot.fm/issues/issue_2004_04/article7 this article].		* Agents look contravarient. But they are not. Believe us. For details and explanations, see [http://www.jot.fm/issues/issue_2004_04/article7 this article].

−	== Differences between ETL2 and ~~LibertyEiffel~~ ==	+	== Differences between ETL2 and the former SmartEiffel ==

−	~~LibertyEiffel~~ was at some time based on ETL2; as all the members of the Eiffel language family, it has grown and improved on that, adding several features (some of them also implemented by other compilers)	+	SmartEiffel was at some time based on ETL2; as all the members of the Eiffel language family, it has grown and improved on that, adding several features (some of them also implemented by other compilers)

	* The "Precursor" mechanism (proposed at OOSC2). see [[Precursor]]		* The "Precursor" mechanism (proposed at OOSC2). see [[Precursor]]

Hzwakenberg at 19:33, 5 September 2014

2014-09-05T19:33:26Z

← Older revision		Revision as of 21:33, 5 September 2014
Line 1:		Line 1:
		+	This page is about language compatibility for LibertyEiffel. You can find here the most important differences between LibertyEiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.
−	[[Category:Smarteiffel]]

		+	== Unique peculiarities of LibertyEiffel ==
−	This page is about language compatibility for SmartEiffel. You can find here the most important differences between SmartEiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.

		+	LibertyEiffel has some features not implemented by any other implementation:
−	== Unique peculiarities of SmartEiffel ==
−
−	SmartEiffel has some features not implemented by any other implementation:

	* Case sensitivity: "abc", "Abc" and "ABC" are different identifiers		* Case sensitivity: "abc", "Abc" and "ABC" are different identifiers
Line 15:		Line 13:
	* New operators for run-time type checking. See [[Dynamic type testing]]		* New operators for run-time type checking. See [[Dynamic type testing]]
	* Removed the danger of automatic boxing (object allocation on assignment of expanded types to reference entities)		* Removed the danger of automatic boxing (object allocation on assignment of expanded types to reference entities)
−	* Lots of additional tools in the library. See [[Table of contents#Library\|The ~~SmartEiffel~~ general purpose library]]	+	* Lots of additional tools in the library. See [[Table of contents#Library\|The LibertyEiffel general purpose library]]
	* Notation for [[Manifest storage notation\|manifest collections]]. The old <code><<...>></code> is still supported for simple arrays.		* Notation for [[Manifest storage notation\|manifest collections]]. The old <code><<...>></code> is still supported for simple arrays.
	* Unicode strings manifest notation.		* Unicode strings manifest notation.
	* Agents look contravarient. But they are not. Believe us. For details and explanations, see [http://www.jot.fm/issues/issue_2004_04/article7 this article].		* Agents look contravarient. But they are not. Believe us. For details and explanations, see [http://www.jot.fm/issues/issue_2004_04/article7 this article].

−	== Differences between ETL2 and ~~SmartEiffel~~ ==	+	== Differences between ETL2 and LibertyEiffel ==

−	~~SmartEiffel~~ was at some time based on ETL2; as all the members of the Eiffel language family, it has grown and improved on that, adding several features (some of them also implemented by other compilers)	+	LibertyEiffel was at some time based on ETL2; as all the members of the Eiffel language family, it has grown and improved on that, adding several features (some of them also implemented by other compilers)

	* The "Precursor" mechanism (proposed at OOSC2). see [[Precursor]]		* The "Precursor" mechanism (proposed at OOSC2). see [[Precursor]]
	* Agents and tuples. see [[Agent]] and [[Tuple]]		* Agents and tuples. see [[Agent]] and [[Tuple]]

−	== Differences between SmartEiffel and ECMA Eiffel ==	+	== Differences between the former SmartEiffel and ECMA Eiffel ==

	The [http://www.ecma-international.org/publications/standards/Ecma-367.htm ECMA Eiffel specification] does not describe any current implementation at the time of writing this (November 2005). Despite being a standard it describes several features that fork away from what has been always called "Eiffel". The following aspects of ECMA Eiffel will not be implemented in SmartEiffel:		The [http://www.ecma-international.org/publications/standards/Ecma-367.htm ECMA Eiffel specification] does not describe any current implementation at the time of writing this (November 2005). Despite being a standard it describes several features that fork away from what has been always called "Eiffel". The following aspects of ECMA Eiffel will not be implemented in SmartEiffel:

Ramack at 21:30, 5 March 2013

2013-03-05T21:30:14Z

← Older revision		Revision as of 23:30, 5 March 2013
Line 1:		Line 1:
−	[[Category:~~SmartEiffel~~]]	+	[[Category:Smarteiffel]]

	This page is about language compatibility for SmartEiffel. You can find here the most important differences between SmartEiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.		This page is about language compatibility for SmartEiffel. You can find here the most important differences between SmartEiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.

Ramack: adding to category SmartEiffel

2013-03-04T19:34:00Z

adding to category SmartEiffel

← Older revision		Revision as of 21:34, 4 March 2013
Line 1:		Line 1:
		+	[[Category:SmartEiffel]]
		+
	This page is about language compatibility for SmartEiffel. You can find here the most important differences between SmartEiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.		This page is about language compatibility for SmartEiffel. You can find here the most important differences between SmartEiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.

Ramack: 9 revisions: initial import from SamrtEiffel Wiki - The Grand SmartEiffel Book

2013-03-03T21:04:30Z

9 revisions: initial import from SamrtEiffel Wiki - The Grand SmartEiffel Book

New page

This page is about language compatibility for SmartEiffel. You can find here the most important differences between SmartEiffel and other similar languages. The list is not intended to be exhaustive, it just intends to highlight the most important differences.

== Unique peculiarities of SmartEiffel ==

SmartEiffel has some features not implemented by any other implementation:

* Case sensitivity: "abc", "Abc" and "ABC" are different identifiers
* Compiler-enforced casing rules: Class names must be all-uppercase; camelCase is not allowed.
* ANY is the root of the inheritance tree, but not of the conformance tree.
* Conformance rules related to expanded types.
* Non-conforming inheritance. See [[Conforming and non-conforming inheritance]]
* The notation for non-conforming inheritance is "insert <Type_Class>".
* New operators for run-time type checking. See [[Dynamic type testing]]
* Removed the danger of automatic boxing (object allocation on assignment of expanded types to reference entities)
* Lots of additional tools in the library. See [[Table of contents#Library|The SmartEiffel general purpose library]]
* Notation for [[Manifest storage notation|manifest collections]]. The old <code><<...>></code> is still supported for simple arrays.
* Unicode strings manifest notation.
* Agents look contravarient. But they are not. Believe us. For details and explanations, see [http://www.jot.fm/issues/issue_2004_04/article7 this article].

== Differences between ETL2 and SmartEiffel ==

SmartEiffel was at some time based on ETL2; as all the members of the Eiffel language family, it has grown and improved on that, adding several features (some of them also implemented by other compilers)

* The "Precursor" mechanism (proposed at OOSC2). see [[Precursor]]
* Agents and tuples. see [[Agent]] and [[Tuple]]

== Differences between SmartEiffel and ECMA Eiffel ==

The [http://www.ecma-international.org/publications/standards/Ecma-367.htm ECMA Eiffel specification] does not describe any current implementation at the time of writing this (November 2005). Despite being a standard it describes several features that fork away from what has been always called "Eiffel". The following aspects of ECMA Eiffel will not be implemented in SmartEiffel:

* Conversions (implemented in ISE Eiffel)
* Feature aliases (implemented in ISE Eiffel)
* Bracket indexing (implemented in ISE Eiffel)
* No-variant agent arguments.

On the other hand, the following features were taken from the ECMA specification process:

* Non-conforming inheritance (although the notation is different)