Compiler

Major changes between ISE Eiffel 7.0 and ISE Eiffel 7.1

What's new

  • New SCOOP processor GC which lets you create as many processors as you want as long as they are no more than 1500 concurrent processors (or less depending on your available memory).
  • Supported the EIFFEL_LIBRARY environment variables to locate libraries.

Improvements

  • The Eiffel Configuration Files accept C compiler and linker flags.

Major changes between ISE Eiffel 6.8 and ISE Eiffel 7.0

What's new

  • Supported development of incomplete void-safe classes (so called "design mode") by avoiding reporting void-safety errors for unreachable code, e.g. for the code after a call to a feature that never returns normally, say, to {EXCEPTIONS}.die. As a result it became possible to declare a creation procedure that does not initialize attached attributes properly (because the corresponding effective classes are not available yet), for example:

make (...)
	do
		...

Major changes between ISE Eiffel 6.6 and ISE Eiffel 6.7

What's new

See Also: Differences between standard ECMA-367 and Eiffel Software implementation

  • EiffelStudio can use GCC on Windows for both 32-bit and 64-bit edition. We are using version 4.4.5 of gcc.
  • EiffelStudio can now parse UTF-8 source code. Unicode characters can be used in strings, comments and operators.
  • New tracing facility for Eiffel code. Until now tracing was done at the runtime level by writing to the standard output.

Definition file

tags:

The syntax is pretty simple when you understand what you need to export a feature: you need the name of the feature, the name of the concerned class, and the name of a creation procedure. What is optional is to specify an alias, an index and a calling convention. The index and calling convention are mainly used to create a DLL for windows, and the alias to export the feature under a different name.

Using a CECIL archive

tags:

Linking the CECIL archive into a program

The CECIL archive already incorporates the Eiffel run-time. To use the functions provided in the CECIL archive, simply write the C programs according to the CECIL specifications of ETL, and then include the CECIL archive in the link line of your C application.


On Unix/linux, this line looks like this:


ld -o [name of your CECIL executable] [your C object files and archives]lib<system name>.a -lm


{{note|On Unix, linking with "-lm" is required since the Eiffel run-time uses the standard math libraries.

Syndicate content