Externals - Revision history

Hzwakenberg at 11:35, 30 July 2024

2024-07-30T11:35:16Z

← Older revision		Revision as of 13:35, 30 July 2024
Line 36:		Line 36:
	== external "built_in" ==		== external "built_in" ==

−	This specification is reserved for the compiler and its base libraries. It is not usable outside of very specific cases unique to [[compile_to_c]] and [[compile_to_jvm]]. These cases are the "building blocks" that produce specialized output code depending on the code generator being used.	+	This specification is reserved for the compiler and its base libraries. It is not usable outside of very specific cases, unique to [[compile_to_c]] and [[compile_to_jvm]]. These cases are the "building blocks" that produce specialized output code depending on the code generator being used.

	For example, <TT>infix "#+"</TT> in the class [[library_class:INTEGER\|<TT>INTEGER</TT>]] is directly translated in C by a <TT>+</TT>, and in Java by the <TT>iadd</TT> bytecode.		For example, <TT>infix "#+"</TT> in the class [[library_class:INTEGER\|<TT>INTEGER</TT>]] is directly translated in C by a <TT>+</TT>, and in Java by the <TT>iadd</TT> bytecode.

Hzwakenberg: /* external types */

2016-03-05T11:51:20Z

external types

← Older revision		Revision as of 13:51, 5 March 2016
Line 42:		Line 42:
	== external types ==		== external types ==

−	A mechanism for embedding [[external types]] from the underlying language is being designed for ~~the~~ ~~2.4~~ release.	+	A mechanism for embedding [[external types]] from the underlying language is being designed for a future release.

	== external "Java" - currently not supported ==		== external "Java" - currently not supported ==

Hzwakenberg at 13:23, 7 September 2014

2014-09-07T13:23:40Z

← Older revision		Revision as of 15:23, 7 September 2014
Line 1:		Line 1:
		+	[[Category: Interfacing]]
	See "External Types".		See "External Types".

Hzwakenberg: /* external "built_in" */

2014-09-07T10:17:52Z

external "built_in"

← Older revision		Revision as of 12:17, 7 September 2014
Line 38:		Line 38:

	For example, <TT>infix "#+"</TT> in the class [[library_class:INTEGER\|<TT>INTEGER</TT>]] is directly translated in C by a <TT>+</TT>, and in Java by the <TT>iadd</TT> bytecode.		For example, <TT>infix "#+"</TT> in the class [[library_class:INTEGER\|<TT>INTEGER</TT>]] is directly translated in C by a <TT>+</TT>, and in Java by the <TT>iadd</TT> bytecode.
−

	== external types ==		== external types ==

Hzwakenberg: /* external "C++" */

2014-09-07T10:17:22Z

external "C++"

← Older revision		Revision as of 12:17, 7 September 2014
Line 23:		Line 23:
	This mechanism is only available with [[compile_to_c]].		This mechanism is only available with [[compile_to_c]].

−	This mechanism has since been supplanted with plugins (see below).	+	This mechanism has since been supplanted with [[plugins]] (see below).

	== external "plug_in" ==		== external "plug_in" ==

Hzwakenberg: /* external "C" */

2014-09-07T10:16:57Z

external "C"

← Older revision		Revision as of 12:16, 7 September 2014
Line 13:		Line 13:
	This mechanism is only available with [[compile_to_c]].		This mechanism is only available with [[compile_to_c]].

−	This mechanism has since been supplanted with plugins (see below).	+	This mechanism has since been supplanted with [[plugins]] (see below).

	== external "C++" ==		== external "C++" ==

Hzwakenberg: /* external "Java" - currently not supported */

2014-09-07T10:15:15Z

external "Java" - currently not supported

← Older revision		Revision as of 12:15, 7 September 2014
Line 46:		Line 46:
	== external "Java" - currently not supported ==		== external "Java" - currently not supported ==

−	This specification would permit calling Java code from Eiffel.	+	This specification would permit calling Java code from Eiffel. Some examples used to be available in the tutorial, <TT>tutorial/external/Java</TT>. This mechanism would only be available with [[compile_to_jvm]], which currently is not supported.
−
−	Some examples are available in the tutorial, <TT>tutorial/external/Java</TT>.
−
−	This mechanism would only be available with [[compile_to_jvm]], which currently is not supported.

	This mechanism has since been supplanted with [[plugins]] (see below).		This mechanism has since been supplanted with [[plugins]] (see below).

Hzwakenberg: /* external "Java" - currently not supported */

2014-09-07T10:13:40Z

external "Java" - currently not supported

← Older revision		Revision as of 12:13, 7 September 2014
Line 46:		Line 46:
	== external "Java" - currently not supported ==		== external "Java" - currently not supported ==

−	This specification ~~permits~~ calling Java code from Eiffel.	+	This specification would permit calling Java code from Eiffel.

	Some examples are available in the tutorial, <TT>tutorial/external/Java</TT>.		Some examples are available in the tutorial, <TT>tutorial/external/Java</TT>.

−	This mechanism is only available with [[compile_to_jvm]].	+	This mechanism would only be available with [[compile_to_jvm]], which currently is not supported.

−	This mechanism has since been supplanted with plugins (see below).	+	This mechanism has since been supplanted with [[plugins]] (see below).

Ramack at 22:18, 23 May 2014

2014-05-23T22:18:18Z

← Older revision		Revision as of 00:18, 24 May 2014
Line 1:		Line 1:
−	[[Category:Smarteiffel]]
−
	See "External Types".		See "External Types".

−	''Externals'' build on top of a standard Eiffel ~~mechanisn~~. This ~~mechanisn~~ permits calling code in a language different from Eiffel.	+	''Externals'' build on top of a standard Eiffel mechanism. This mechanism permits calling code in a language different from Eiffel.

−	You will find below the current list of ''external'' specifications supported by ~~SmartEiffel~~.	+	You will find below the current list of ''external'' specifications supported by Liberty.

	== external "C" ==		== external "C" ==

−	This specification permits calling C code from Eiffel. This ~~mechanisn~~ is described in [[Bibliography#ETL_1992\|''Eiffel: The Language'']].	+	This specification permits calling C code from Eiffel. This mechanism is described in [[Bibliography#ETL_1992\|''Eiffel: The Language'']].

	Some examples are available in the tutorial, <TT>tutorial/external/C</TT>.		Some examples are available in the tutorial, <TT>tutorial/external/C</TT>.

−	This ~~mechanisn~~ is only available with [[compile_to_c]].	+	This mechanism is only available with [[compile_to_c]].

	This mechanism has since been supplanted with plugins (see below).		This mechanism has since been supplanted with plugins (see below).
Line 24:		Line 22:

	This mechanism is only available with [[compile_to_c]].		This mechanism is only available with [[compile_to_c]].
−
−	This mechanism has since been supplanted with plugins (see below).
−
−	== external "Java" ==
−
−	This specification permits calling Java code from Eiffel.
−
−	Some examples are available in the tutorial, <TT>tutorial/external/Java</TT>.
−
−	This mechanism is only available with [[compile_to_jvm]].

	This mechanism has since been supplanted with plugins (see below).		This mechanism has since been supplanted with plugins (see below).
Line 39:		Line 27:
	== external "plug_in" ==		== external "plug_in" ==

−	This specification is particularly utilized y the ~~SmartEiffel~~ standard libraries. This form is preferred to ''external "C"'' and ''external "Java"''.	+	This specification is particularly utilized by the Liberty standard libraries. This form is preferred to ''external "C"'' and ''external "Java"''.

	Examples are available throughout the standard library.		Examples are available throughout the standard library.
Line 47:		Line 35:
	== external "built_in" ==		== external "built_in" ==

−	This specification is reserved for the ~~SmartEiffel~~ compiler. It is not usable outside of very specific cases unique to [[compile_to_c]] and [[compile_to_jvm]]. These cases are the "building blocks" that produce specialized output code depending on the code generator being used.	+	This specification is reserved for the compiler and its base libraries. It is not usable outside of very specific cases unique to [[compile_to_c]] and [[compile_to_jvm]]. These cases are the "building blocks" that produce specialized output code depending on the code generator being used.

	For example, <TT>infix "#+"</TT> in the class [[library_class:INTEGER\|<TT>INTEGER</TT>]] is directly translated in C by a <TT>+</TT>, and in Java by the <TT>iadd</TT> bytecode.		For example, <TT>infix "#+"</TT> in the class [[library_class:INTEGER\|<TT>INTEGER</TT>]] is directly translated in C by a <TT>+</TT>, and in Java by the <TT>iadd</TT> bytecode.
Line 55:		Line 43:

	A mechanism for embedding [[external types]] from the underlying language is being designed for the 2.4 release.		A mechanism for embedding [[external types]] from the underlying language is being designed for the 2.4 release.
		+
		+	== external "Java" - currently not supported ==
		+
		+	This specification permits calling Java code from Eiffel.
		+
		+	Some examples are available in the tutorial, <TT>tutorial/external/Java</TT>.
		+
		+	This mechanism is only available with [[compile_to_jvm]].
		+
		+	This mechanism has since been supplanted with plugins (see below).

Ramack at 21:10, 4 March 2013

2013-03-04T21:10:30Z

← Older revision		Revision as of 23:10, 4 March 2013
Line 1:		Line 1:
−	[[Category:~~Book~~]]	+	[[Category:Smarteiffel]]
		+
		+	See "External Types".

	''Externals'' build on top of a standard Eiffel mechanisn. This mechanisn permits calling code in a language different from Eiffel.		''Externals'' build on top of a standard Eiffel mechanisn. This mechanisn permits calling code in a language different from Eiffel.