mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2026-04-04 17:19:23 +02:00
Code Issues Packages Projects Releases Wiki Activity

Author:halw

Browse Source 
Date:2008-09-25T01:53:30.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@42 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2008-09-25 01:53:30 +00:00
parent 24ad6cc4ac
commit c9b9c2adcd
19 changed files with 49 additions and 82 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/index.wiki
View File

@@ -1,12 +1,17 @@
[[Property:title|The Eiffel for .NET language]]
[[Property:weight|2]]
[[Property:uuid|ba6cd8d3-683c-4167-bdef-a0274c392f34]]
* [[Eiffel for .NET: Introduction|Introduction]]
* [[Eiffel for .NET Conventions|Using Eiffel on .NET]]
* [[Eiffel for .NET|Summary of the Eiffel Language]]
* [[Eiffel for .NET Limitations|Difference between Eiffel and Eiffel for .NET]]
* [[Known issues|Known issues with Eiffel for .NET compiler]]
This section focuses on defining Eiffel for .NET. The key requirement for Eiffel for .NET is the exclusive use of the common language runtime with a minimum Eiffel-specific runtime. The second requirement is to generate IL code that is CLS compliant, meaning that other CLS compliant languages/compilers/tools will be able to reuse .NET components written in Eiffel for .NET. The last requirement is to generate verifiable IL code.
Because not all Eiffel functionalities are present in .NET, the task of the Eiffel compiler is made more complicated since it has to emulate those mechanisms instead of reusing what .NET provides. For example the common language runtime of .NET does not support:
* multiple inheritance
* genericity
* covariance
* agents
We will see:
* what is Eiffel on .NET
* which Eiffel mechanisms have been implemented and which haven't.