mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-06 23:02:28 +01:00
Code Issues Packages Projects Releases Wiki Activity

Author:vwheeler

Browse Source 
Date:2014-02-09T23:16:22.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1258 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
vwheeler
2014-02-11 22:18:32 +00:00
parent 99a8747e6c
commit 6713a9fc93
2 changed files with 27 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
documentation/current/guide/index.wiki
View File

@@ -141,6 +141,7 @@ There is no better place to gain an in-depth understanding of the Eiffel softwar
Eiffel has been standardized under ISO and ECMA. The comprehensive description of the standard Eiffel programming language is presented in [http://www.ecma-international.org/publications/standards/Ecma-367.htm Standard ECMA-367].
----
===Contribute to Eiffel===
@@ -155,3 +156,26 @@ You can help Eiffel by contributing your time, expertise, and products. Here are
:[http://eiffelstudio.origo.ethz.ch/ EiffelStudio on Origo] contains blogs and forums focusing on Eiffel and EiffelStudio topics.
----
==[[Glossary of Object Technology]]==
----
This is a relatively comprehensive glossary of terms used in Object-Oriented Analysis, Design, and programming, but are not specific to the Eiffel Language, since object-oriented principles can be applied to any programming language. It contains all the terms from the glossary in [[Object-Oriented Software Construction, 2nd Edition]], plus others used in this website, added for clarity and ease of reference.
This glossary is useful all by itself, since a review of it can serve as a refresher (in case you have been away from Object Technology for a while). It is used in this website to assist the reader by providing easy links to technical terms that are used throughout the website.
Additionally, it is possible to link to terms in this glossary from other websites by using links that look like this:
:<nowiki>http://docs.eiffel.com/book/guide/glossary-object-technology#Attribute.</nowiki>
Note that the anchor (the part after the "#") has to be spelled and capitalized exactly like the term on the page. (Use underscore characters to replace spaces.)
----

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

@@ -4,9 +4,9 @@
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
* [[Glossary of Object Technology#Multiple inheritance|multiple inheritance]]
* [[Glossary of Object Technology#Genericity|genericity]]
* [[Glossary of Object Technology#Covariance|covariance]]
* agents
We will see: