Cecil - Revision history

Dkearns: s/LibertyEiffel/Liberty Eiffel/

2016-06-22T02:01:06Z

s/LibertyEiffel/Liberty Eiffel/

← Older revision		Revision as of 04:01, 22 June 2016
Line 2:		Line 2:
	Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].		Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].

−	In order to call Eiffel from C, you must use the flag <TT>-cecil <cecil_file></TT> with [[compile]] or [[compile_to_c]]. The file <TT><cecil_file></TT> must give the list of [[Glossary#Feature\|features]] that you want to call from C. The stub routines are automatically generated by ~~LibertyEiffel~~.	+	In order to call Eiffel from C, you must use the flag <TT>-cecil <cecil_file></TT> with [[compile]] or [[compile_to_c]]. The file <TT><cecil_file></TT> must give the list of [[Glossary#Feature\|features]] that you want to call from C. The stub routines are automatically generated by Liberty Eiffel.

	When the flag <TT>-cecil</TT> is used, [[compile_to_c]] also produces one more C header file, which contains all stub routine prototypes.		When the flag <TT>-cecil</TT> is used, [[compile_to_c]] also produces one more C header file, which contains all stub routine prototypes.

Hzwakenberg at 13:20, 7 September 2014

2014-09-07T13:20:57Z

← Older revision		Revision as of 15:20, 7 September 2014
Line 1:		Line 1:
		+	[[Category: Interfacing]]
	Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].		Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].

Hzwakenberg at 19:29, 5 September 2014

2014-09-05T19:29:13Z

← Older revision		Revision as of 21:29, 5 September 2014
Line 1:		Line 1:
−	[[Category:Smarteiffel]]
−
	Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].		Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].

−	In order to call Eiffel from C, you must use the flag <TT>-cecil <cecil_file></TT> with [[compile]] or [[compile_to_c]]. The file <TT><cecil_file></TT> must give the list of [[Glossary#Feature\|features]] that you want to call from C. The stub routines are automatically generated by ~~SmartEiffel~~.	+	In order to call Eiffel from C, you must use the flag <TT>-cecil <cecil_file></TT> with [[compile]] or [[compile_to_c]]. The file <TT><cecil_file></TT> must give the list of [[Glossary#Feature\|features]] that you want to call from C. The stub routines are automatically generated by LibertyEiffel.

	When the flag <TT>-cecil</TT> is used, [[compile_to_c]] also produces one more C header file, which contains all stub routine prototypes.		When the flag <TT>-cecil</TT> is used, [[compile_to_c]] also produces one more C header file, which contains all stub routine prototypes.

Ramack at 21:23, 5 March 2013

2013-03-05T21:23:41Z

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

	Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].		Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].

Ramack at 20:52, 4 March 2013

2013-03-04T20:52:36Z

← Older revision		Revision as of 22:52, 4 March 2013
Line 1:		Line 1:
−	[[Category:~~Book~~]]	+	[[Category:SmartEiffel]]

	Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].		Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].

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

2013-03-03T21:04:27Z

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

← Older revision	Revision as of 23:04, 3 March 2013
(No difference)

Cadrian: update on type liveliness when using creation features

2007-03-07T09:18:14Z

update on type liveliness when using creation features

← Older revision		Revision as of 11:18, 7 March 2007
Line 33:		Line 33:
	X_f X f		X_f X f

		+	Please note that
−	Please note that the <TT><type_eiffel></TT> must be a [[Glossary#LiveType\|'''live type''']]. For example, if the <TT><eiffel_type></TT> is [[library_class:ARRAY\|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER\|<TT>INTEGER</TT>]]<TT>]</TT>, your Eiffel program must at least create one instance of type [[library_class:ARRAY\|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER\|<TT>INTEGER</TT>]]<TT>]</TT>. Of course, if the called feature is a creation procedure, then the corresponding type is made alive.
		+	* for "normal" features the <TT><type_eiffel></TT> must be a [[Glossary#LiveType\|live type]]
		+	* for "creation" features the <TT><type_eiffel></TT> will be made [[Glossary#LiveType\|alive]].
		+
		+	For example, if the <TT><eiffel_type></TT> is [[library_class:ARRAY\|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER\|<TT>INTEGER</TT>]]<TT>]</TT>, your Eiffel program must at least create one instance of type [[library_class:ARRAY\|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER\|<TT>INTEGER</TT>]]<TT>]</TT>. Of course, if the called feature is a creation procedure, then the corresponding type is made alive.

	The name of the [[Glossary#Feature\|feature]] to call, <TT><feature_name></TT>, can be a prefix or infix name. The [[Syntax_diagrams#FeatureName\|syntax]] is the same as the one used in the Eiffel source code.		The name of the [[Glossary#Feature\|feature]] to call, <TT><feature_name></TT>, can be a prefix or infix name. The [[Syntax_diagrams#FeatureName\|syntax]] is the same as the one used in the Eiffel source code.

Cadrian: what does Cecil mean

2006-07-24T11:07:38Z

what does Cecil mean

← Older revision		Revision as of 13:07, 24 July 2006
Line 1:		Line 1:
	[[Category:Book]]		[[Category:Book]]

−	Cecil is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].	+	Cecil (C-Eiffel Call-In Library) is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].

	In order to call Eiffel from C, you must use the flag <TT>-cecil <cecil_file></TT> with [[compile]] or [[compile_to_c]]. The file <TT><cecil_file></TT> must give the list of [[Glossary#Feature\|features]] that you want to call from C. The stub routines are automatically generated by SmartEiffel.		In order to call Eiffel from C, you must use the flag <TT>-cecil <cecil_file></TT> with [[compile]] or [[compile_to_c]]. The file <TT><cecil_file></TT> must give the list of [[Glossary#Feature\|features]] that you want to call from C. The stub routines are automatically generated by SmartEiffel.

Cadrian: create

2006-07-24T10:55:50Z

create

← Older revision		Revision as of 12:55, 24 July 2006
Line 9:		Line 9:
	Your <TT><cecil_file></TT> file must contain at least two lines. The first line is the name of the C header file to produce (a <TT>.h</TT> file). The other lines have the following structure:		Your <TT><cecil_file></TT> file must contain at least two lines. The first line is the name of the C header file to produce (a <TT>.h</TT> file). The other lines have the following structure:

−	<c_name> <eiffel_type> <feature_name> {create\|creation}	+	<c_name> <eiffel_type> <feature_name> {create\|creation}

	The <TT><c_name></TT> is the name of the C stub routine that wraps the Eiffel call. The couple <TT><eiffel_type> <feature_name></TT> gives the complete name of the Eiffel [[Glossary#Feature\|feature]] to call.		The <TT><c_name></TT> is the name of the C stub routine that wraps the Eiffel call. The couple <TT><eiffel_type> <feature_name></TT> gives the complete name of the Eiffel [[Glossary#Feature\|feature]] to call.
Line 16:		Line 16:
	* the <TT><eiffel_type></TT> must not be deferred		* the <TT><eiffel_type></TT> must not be deferred
	* the <TT><feature_name></TT> must be the one of a creation procedure listed in one of the creation clauses of the class; the client exports are not checked (i.e. a <TT>create {}</TT> clause can be useful in that case)		* the <TT><feature_name></TT> must be the one of a creation procedure listed in one of the creation clauses of the class; the client exports are not checked (i.e. a <TT>create {}</TT> clause can be useful in that case)
		+	* the <TT><c_name></TT> generated C function returns the created object

	You can also put Eiffel-style comments.		You can also put Eiffel-style comments.
Line 25:		Line 26:
	StringItem STRING item		StringItem STRING item
	StringGT STRING infix ">"		StringGT STRING infix ">"
		+	StringNew SRING make create
	-- features from ARRAY[INTEGER] :		-- features from ARRAY[INTEGER] :
	IntArrayCount ARRAY[INTEGER] count		IntArrayCount ARRAY[INTEGER] count
Line 31:		Line 33:
	X_f X f		X_f X f

−	Please note that the <TT><type_eiffel></TT> must be a [[Glossary#LiveType\|'''live type''']]. For example, if the <TT><eiffel_type></TT> is [[library_class:ARRAY\|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER\|<TT>INTEGER</TT>]]<TT>]</TT>, your Eiffel program must at least create one instance of type [[library_class:ARRAY\|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER\|<TT>INTEGER</TT>]]<TT>]</TT>.	+	Please note that the <TT><type_eiffel></TT> must be a [[Glossary#LiveType\|'''live type''']]. For example, if the <TT><eiffel_type></TT> is [[library_class:ARRAY\|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER\|<TT>INTEGER</TT>]]<TT>]</TT>, your Eiffel program must at least create one instance of type [[library_class:ARRAY\|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER\|<TT>INTEGER</TT>]]<TT>]</TT>. Of course, if the called feature is a creation procedure, then the corresponding type is made alive.

	The name of the [[Glossary#Feature\|feature]] to call, <TT><feature_name></TT>, can be a prefix or infix name. The [[Syntax_diagrams#FeatureName\|syntax]] is the same as the one used in the Eiffel source code.		The name of the [[Glossary#Feature\|feature]] to call, <TT><feature_name></TT>, can be a prefix or infix name. The [[Syntax_diagrams#FeatureName\|syntax]] is the same as the one used in the Eiffel source code.

−	Nota bene:	+	''Nota bene:''
−	* ~~since~~ attributes are [[Glossary#Feature\|features]], it is of course possible to access them with this mechanism.	+	* Since attributes are [[Glossary#Feature\|features]], it is of course possible to access them with this mechanism.
	* The [[Glossary#LateBinding\|late binding]] is also taken in account. In the above example, a call to <TT>X_f()</TT> in C is equivalent to the call <TT>x.f</TT> in Eiffel, with <TT>x</TT> of type <TT>X</TT> ''or a descendant of <TT>X</TT>''.		* The [[Glossary#LateBinding\|late binding]] is also taken in account. In the above example, a call to <TT>X_f()</TT> in C is equivalent to the call <TT>x.f</TT> in Eiffel, with <TT>x</TT> of type <TT>X</TT> ''or a descendant of <TT>X</TT>''.

Line 48:		Line 50:
	cry ANIMAL cry		cry ANIMAL cry
	string_to_external STRING to_external		string_to_external STRING to_external
		+
		+	Note that Cecil files can also be automatically included by C [[plugins]].

Cadrian: create

2006-07-24T09:32:29Z

create

New page

[[Category:Book]]

Cecil is a mechanism that permits to call Eiffel code from C. In this way, it is the opposite of [[externals]].

In order to call Eiffel from C, you must use the flag <TT>-cecil <cecil_file></TT> with [[compile]] or [[compile_to_c]]. The file <TT><cecil_file></TT> must give the list of [[Glossary#Feature|features]] that you want to call from C. The stub routines are automatically generated by SmartEiffel.

When the flag <TT>-cecil</TT> is used, [[compile_to_c]] also produces one more C header file, which contains all stub routine prototypes.

Your <TT><cecil_file></TT> file must contain at least two lines. The first line is the name of the C header file to produce (a <TT>.h</TT> file). The other lines have the following structure:

<c_name> <eiffel_type> <feature_name> {create|creation}

The <TT><c_name></TT> is the name of the C stub routine that wraps the Eiffel call. The couple <TT><eiffel_type> <feature_name></TT> gives the complete name of the Eiffel [[Glossary#Feature|feature]] to call.

The <TT>create</TT> (or <TT>creation</TT>) optional keyword at the end of the line indicates that the given feature is used as a constructor. In that case the following rules apply:
* the <TT><eiffel_type></TT> must not be deferred
* the <TT><feature_name></TT> must be the one of a creation procedure listed in one of the creation clauses of the class; the client exports are not checked (i.e. a <TT>create {}</TT> clause can be useful in that case)

You can also put Eiffel-style comments.

For example:

-- features from STRING :
StringIsEmpty STRING empty
StringItem STRING item
StringGT STRING infix ">"
-- features from ARRAY[INTEGER] :
IntArrayCount ARRAY[INTEGER] count
IntArrayItem ARRAY[INTEGER] item
-- features from X :
X_f X f

Please note that the <TT><type_eiffel></TT> must be a [[Glossary#LiveType|'''live type''']]. For example, if the <TT><eiffel_type></TT> is [[library_class:ARRAY|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER|<TT>INTEGER</TT>]]<TT>]</TT>, your Eiffel program must at least create one instance of type [[library_class:ARRAY|<TT>ARRAY</TT>]]<TT>[</TT>[[library_class:INTEGER|<TT>INTEGER</TT>]]<TT>]</TT>.

The name of the [[Glossary#Feature|feature]] to call, <TT><feature_name></TT>, can be a prefix or infix name. The [[Syntax_diagrams#FeatureName|syntax]] is the same as the one used in the Eiffel source code.

Nota bene:
* since attributes are [[Glossary#Feature|features]], it is of course possible to access them with this mechanism.
* The [[Glossary#LateBinding|late binding]] is also taken in account. In the above example, a call to <TT>X_f()</TT> in C is equivalent to the call <TT>x.f</TT> in Eiffel, with <TT>x</TT> of type <TT>X</TT> ''or a descendant of <TT>X</TT>''.

Here is another example of a Cecil file (more can be found in the tutorial <TT>SmartEiffel/tutorial/cecil</TT>):
-- The name of the include C file:
eiffel.h
-- The features you want to call from C:
array_of_animal_item ARRAY[ANIMAL] item
array_of_animal_lower ARRAY[ANIMAL] lower
array_of_animal_upper ARRAY[ANIMAL] upper
cry ANIMAL cry
string_to_external STRING to_external