Compile to c - Revision history

Hzwakenberg at 15:21, 7 July 2024

2024-07-07T15:21:30Z

← Older revision		Revision as of 17:21, 7 July 2024
Line 168:		Line 168:
	\|-		\|-
	\| valign="top" \| <code>-gc_info</code>		\| valign="top" \| <code>-gc_info</code>
−	\| When this option is used, the [[garbage collector]] displays ~~at run time some~~ information about its use.	+	\| When this option is used, the [[garbage collector]] displays information about its use at run time.
	\|-		\|-
	\| valign="top" \| <code>-cecil <cecil_file></code>		\| valign="top" \| <code>-cecil <cecil_file></code>

Hzwakenberg: /* Common options */

2018-08-29T11:07:32Z

Common options

← Older revision		Revision as of 13:07, 29 August 2018
Line 40:		Line 40:
	\|-		\|-
	\| valign="top" \| <code>-version</code>		\| valign="top" \| <code>-version</code>
−	\| Display the ~~SmartEiffel~~ version number.	+	\| Display the Liberty Eiffel version number.
	\|}		\|}

Hzwakenberg at 08:31, 15 June 2016

2016-06-15T08:31:15Z

← Older revision		Revision as of 10:31, 15 June 2016
Line 139:		Line 139:
	\|-		\|-
	\| valign="top" \| <code>-relax</code>		\| valign="top" \| <code>-relax</code>
−	\| Perform ~~less~~ checks by considering less dead code, hence using less memory and less compilation time. Useful to prototype or to deliver safe code. (Useful too for very small computers.)	+	\| Perform fewer checks by considering less dead code, hence using less memory and less compilation time. Useful to prototype or to deliver safe code. (Useful too for very small computers.)
	\|}		\|}

Hzwakenberg: document -relax switch

2016-06-14T19:42:53Z

document -relax switch

← Older revision		Revision as of 21:42, 14 June 2016
Line 139:		Line 139:
	\|-		\|-
	\| valign="top" \| <code>-relax</code>		\| valign="top" \| <code>-relax</code>
		+	\| Perform less checks by considering less dead code, hence using less memory and less compilation time. Useful to prototype or to deliver safe code. (Useful too for very small computers.)
−	\| '''?????''' <!-- Philippe or Dominique, please complete this -->
	\|}		\|}

Dkearns: Document -flymake_mode

2016-06-14T16:47:43Z

Document -flymake_mode

← Older revision		Revision as of 18:47, 14 June 2016
Line 103:		Line 103:
	{\| cellspacing="4" cellpadding="0" width="100%"		{\| cellspacing="4" cellpadding="0" width="100%"
	\|-		\|-
−	\| width="20%" valign="top" \| <code>-~~no_style_warning~~</code>	+	\| width="20%" valign="top" \| <code>-style_warning</code>
−	\| ~~Suppress the display of~~ warning messages about non-compliance with Eiffel style rules ~~''(this flag does not have any effect any more in 2.3)''~~.	+	\| Display warning messages about non-compliance with Eiffel style rules.
	\|-		\|-
	\| valign="top" \| <code>-no_warning</code>		\| valign="top" \| <code>-no_warning</code>
−	\| Suppress all warning messages~~. This implies <TT>-no_style_warning</TT>~~.	+	\| Suppress all warning messages.
		+	\|}
		+
		+	==== Message Styles ====
		+
		+	{\| cellspacing="4" cellpadding="0" width="100%"
		+	\|-
		+	\| width="20%" valign="top" \| <code>-flymake_mode</code>
		+	\| Display messages in a compact format suitable for processing by tools such as Emacs' Flymake mode.
	\|}		\|}

Dkearns: s/method/feature/;s/LibertyEiffel/Liberty Eiffel/

2016-06-08T12:15:13Z

s/method/feature/;s/LibertyEiffel/Liberty Eiffel/

Hzwakenberg: /* Affecting the generated C code */

2016-03-04T17:24:33Z

Affecting the generated C code

← Older revision		Revision as of 19:24, 4 March 2016
Line 154:		Line 154:
	When this option is used, the garbage collector is not produced and (at least) one <TT>malloc()</TT> is done for each object creation. This option is useful if you want to use another garbage collector from an external library, or when a garbage collector is not needed.		When this option is used, the garbage collector is not produced and (at least) one <TT>malloc()</TT> is done for each object creation. This option is useful if you want to use another garbage collector from an external library, or when a garbage collector is not needed.

−	Without this option, ~~Liberty Eiffel~~ builds a garbage collector tailored to the application or the BDW GC.	+	Without this option, LibertyEiffel builds a garbage collector tailored to the application or the BDW GC.
	\|-		\|-
	\| valign="top" \| <code>-bdw_gc</code>		\| valign="top" \| <code>-bdw_gc</code>
Line 171:		Line 171:
	\|-		\|-
	\| valign="top" \| <code>-sedb</code>		\| valign="top" \| <code>-sedb</code>
−	\| This option allows you to include the [[sedb\|~~Liberty Eiffel~~ debugger]] in your executable.	+	\| This option allows you to include the [[sedb\|LibertyEiffel debugger]] in your executable.
	\|-		\|-
	\| valign="top" \| <code>-profile</code>		\| valign="top" \| <code>-profile</code>

Hzwakenberg: /* Affecting the generated C code */

2016-03-04T17:23:17Z

Affecting the generated C code

← Older revision		Revision as of 19:23, 4 March 2016
Line 154:		Line 154:
	When this option is used, the garbage collector is not produced and (at least) one <TT>malloc()</TT> is done for each object creation. This option is useful if you want to use another garbage collector from an external library, or when a garbage collector is not needed.		When this option is used, the garbage collector is not produced and (at least) one <TT>malloc()</TT> is done for each object creation. This option is useful if you want to use another garbage collector from an external library, or when a garbage collector is not needed.

−	Without this option, ~~SmartEiffel~~ builds a garbage collector tailored to the application or the BDW GC.	+	Without this option, Liberty Eiffel builds a garbage collector tailored to the application or the BDW GC.
	\|-		\|-
	\| valign="top" \| <code>-bdw_gc</code>		\| valign="top" \| <code>-bdw_gc</code>
Line 171:		Line 171:
	\|-		\|-
	\| valign="top" \| <code>-sedb</code>		\| valign="top" \| <code>-sedb</code>
−	\| This option allows you to include the [[sedb\|~~SmartEiffel~~ debugger]] in your executable.	+	\| This option allows you to include the [[sedb\|Liberty Eiffel debugger]] in your executable.
	\|-		\|-
	\| valign="top" \| <code>-profile</code>		\| valign="top" \| <code>-profile</code>

Hzwakenberg: /* Compilation mode */

2015-10-08T10:34:08Z

Compilation mode

← Older revision		Revision as of 12:34, 8 October 2015
Line 49:		Line 49:
	There are the following compilation modes which give different levels of assertion checking. In ascending order of verification they are:		There are the following compilation modes which give different levels of assertion checking. In ascending order of verification they are:
	* '''boost''' is a mode in which ''no'' validity checking is done and in which LibertyEiffel does '''additional processing''' compared to the other modes. In particular, in this mode:		* '''boost''' is a mode in which ''no'' validity checking is done and in which LibertyEiffel does '''additional processing''' compared to the other modes. In particular, in this mode:
−	** the execution stack is not managed by ~~SmartEiffel~~,	+	** the execution stack is not managed by LibertyEiffel,
	** the behavior of certain language constructs is changed:		** the behavior of certain language constructs is changed:
	*** no tests for Void (which leads to a segfault if there is any problem...)		*** no tests for Void (which leads to a segfault if there is any problem...)

Hzwakenberg: /* Synopsis */

2015-10-08T10:32:48Z

Synopsis

← Older revision		Revision as of 12:32, 8 October 2015
Line 17:		Line 17:
	In ACE mode, the name of the [[ACE]] file must end with the suffix <TT>.ace</TT>.		In ACE mode, the name of the [[ACE]] file must end with the suffix <TT>.ace</TT>.

−	The <TT>[[compile_to_c]]</TT> command produces the C files (<TT>.h</TT> and <TT>.c</TT>). A script file is also created, whose name depends on the application. This is a <TT>.make</TT> file (under UNIX) or a <TT>.BAT</TT> file (under DOS).	+	The <TT>[[compile_to_c]]</TT> command produces the C files (<TT>.h</TT> and <TT>.c</TT>). A script file is also created, whose name depends on the application. This is a <TT>.make</TT> file (under UNIX) or a <TT>.BAT</TT> file (under DOS/Windows).

	The <TT>[[compile_to_c]]</TT> command must have at least one argument which specifies the program's starting point; this is in fact a class's creation procedure. In ACE mode this data is obtained from parameters in the ACE file. In traditional mode, at least the class name must be specified; the default name of the creation class is <TT>make</TT>, which has to exist; otherwise, the creation method must be specified.		The <TT>[[compile_to_c]]</TT> command must have at least one argument which specifies the program's starting point; this is in fact a class's creation procedure. In ACE mode this data is obtained from parameters in the ACE file. In traditional mode, at least the class name must be specified; the default name of the creation class is <TT>make</TT>, which has to exist; otherwise, the creation method must be specified.

← Older revision		Revision as of 14:15, 8 June 2016
Line 19:		Line 19:
	The <TT>[[compile_to_c]]</TT> command produces the C files (<TT>.h</TT> and <TT>.c</TT>). A script file is also created, whose name depends on the application. This is a <TT>.make</TT> file (under UNIX) or a <TT>.BAT</TT> file (under DOS/Windows).		The <TT>[[compile_to_c]]</TT> command produces the C files (<TT>.h</TT> and <TT>.c</TT>). A script file is also created, whose name depends on the application. This is a <TT>.make</TT> file (under UNIX) or a <TT>.BAT</TT> file (under DOS/Windows).

−	The <TT>[[compile_to_c]]</TT> command must have at least one argument which specifies the program's starting point; this is in fact a class's creation procedure. In ACE mode this data is obtained from parameters in the ACE file. In traditional mode, at least the class name must be specified; the default name of the creation class is <TT>make</TT>, which has to exist; otherwise, the creation ~~method~~ must be specified.	+	The <TT>[[compile_to_c]]</TT> command must have at least one argument which specifies the program's starting point; this is in fact a class's creation procedure. In ACE mode this data is obtained from parameters in the ACE file. In traditional mode, at least the class name must be specified; the default name of the creation class is <TT>make</TT>, which has to exist; otherwise, the creation feature must be specified.

−	In all cases, the creation ~~method~~ must be one ''without arguments''.	+	In all cases, the creation feature must be one ''without arguments''.

	=== Loading Eiffel files ===		=== Loading Eiffel files ===
Line 48:		Line 48:

	There are the following compilation modes which give different levels of assertion checking. In ascending order of verification they are:		There are the following compilation modes which give different levels of assertion checking. In ascending order of verification they are:
−	* '''boost''' is a mode in which ''no'' validity checking is done and in which ~~LibertyEiffel~~ does '''additional processing''' compared to the other modes. In particular, in this mode:	+	* '''boost''' is a mode in which ''no'' validity checking is done and in which Liberty Eiffel does '''additional processing''' compared to the other modes. In particular, in this mode:
−	** the execution stack is not managed by ~~LibertyEiffel~~,	+	** the execution stack is not managed by Liberty Eiffel,
	** the behavior of certain language constructs is changed:		** the behavior of certain language constructs is changed:
	*** no tests for Void (which leads to a segfault if there is any problem...)		*** no tests for Void (which leads to a segfault if there is any problem...)
Line 55:		Line 55:
	*** if <TT>else</TT> is missing from an <TT>inspect</TT> clause, the last branch is used for <TT>else</TT>,		*** if <TT>else</TT> is missing from an <TT>inspect</TT> clause, the last branch is used for <TT>else</TT>,
	** <TT>and</TT> and <TT>or</TT> become semi-strict (i.e. the second expression may not be evaluated if the first expression is enough to infer the result of the <TT>and</TT> or <TT>or</TT> expression, like <TT>and than</TT> and <TT>or else</TT>)		** <TT>and</TT> and <TT>or</TT> become semi-strict (i.e. the second expression may not be evaluated if the first expression is enough to infer the result of the <TT>and</TT> or <TT>or</TT> expression, like <TT>and than</TT> and <TT>or else</TT>)
−	** ~~LibertyEiffel~~ does an optimization pass; in particular, certain functions are inlined;	+	** Liberty Eiffel does an optimization pass; in particular, certain functions are inlined;
	* '''no_check''' is a mode in which no validity checking is done, but the above optimizations are not done (in particular, the execution stack is always managed, the <TT>Void</TT> tests and type checks are always done, and so on);		* '''no_check''' is a mode in which no validity checking is done, but the above optimizations are not done (in particular, the execution stack is always managed, the <TT>Void</TT> tests and type checks are always done, and so on);
	* '''require_check''' is a mode in which only the preconditions are checked;		* '''require_check''' is a mode in which only the preconditions are checked;
Line 154:		Line 154:
	When this option is used, the garbage collector is not produced and (at least) one <TT>malloc()</TT> is done for each object creation. This option is useful if you want to use another garbage collector from an external library, or when a garbage collector is not needed.		When this option is used, the garbage collector is not produced and (at least) one <TT>malloc()</TT> is done for each object creation. This option is useful if you want to use another garbage collector from an external library, or when a garbage collector is not needed.

−	Without this option, ~~LibertyEiffel~~ builds a garbage collector tailored to the application or the BDW GC.	+	Without this option, Liberty Eiffel builds a garbage collector tailored to the application or the BDW GC.
	\|-		\|-
	\| valign="top" \| <code>-bdw_gc</code>		\| valign="top" \| <code>-bdw_gc</code>
Line 166:		Line 166:
	\|-		\|-
	\| valign="top" \| <code>-no_main</code>		\| valign="top" \| <code>-no_main</code>
−	\| Do not generate a <TT>main()</TT> C function. In this case the root creation ~~method~~ is not called. This can be useful when you want to start execution from outside before calling Eiffel routines via the [[cecil]] interface.	+	\| Do not generate a <TT>main()</TT> C function. In this case the root creation feature is not called. This can be useful when you want to start execution from outside before calling Eiffel routines via the [[cecil]] interface.

	Before calling the first Eiffel routine, do not forget to call the routine <TT>initialize_eiffel_runtime(argc, argv);</TT> which initialises the Eiffel system.		Before calling the first Eiffel routine, do not forget to call the routine <TT>initialize_eiffel_runtime(argc, argv);</TT> which initialises the Eiffel system.
	\|-		\|-
	\| valign="top" \| <code>-sedb</code>		\| valign="top" \| <code>-sedb</code>
−	\| This option allows you to include the [[sedb\|~~LibertyEiffel~~ debugger]] in your executable.	+	\| This option allows you to include the [[sedb\|Liberty Eiffel debugger]] in your executable.
	\|-		\|-
	\| valign="top" \| <code>-profile</code>		\| valign="top" \| <code>-profile</code>