mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-07 15:22:31 +01:00
Code Issues Packages Projects Releases Wiki Activity

Author:halw

Browse Source 
Date:2008-09-27T00:55:43.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@51 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2008-09-27 00:55:43 +00:00
parent f7e0dc22f4
commit 0b84f03149
2 changed files with 5 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-classes.wiki
View File

@@ -15,17 +15,9 @@ Having read the above, you should be convinced that the concept of class is impo
Let's take a look at how classes are structured.
==Structure of a Class==
The code that makes up an Eiffel class is divided into the following parts:
* [[#indexing|Indexing]]
* [[#class header|Class header]]
* [[#formal generics|Formal generics]]
* [[#obsolete|Obsolete]]
* [[#inheritance|Inheritance]]
* [[#creators|Creators]]
* [[#features|Features]]
* [[#invariant|Invariant]]
==Structure of a Class==
All of the above, except Class header, are optional. So the simplest Eiffel class you could build would look like this:
<code>
@@ -209,7 +201,7 @@ You may declare multiple <code> feature </code> statements. This helps you group
Although the words " <code> Initialization </code>" and " <code> Access </code>" are actually in comments after the <code> feature </code> keyword, some language processing tools apply some significance to these, for example, ordering the groups in "pretty-printed" views of a class. Also, some tools allow you to build templates for creating new classes which have <code> feature </code> clauses already in place for predetermined groups.
{{tip|There is not a technical requirement governing the grouping or ordering of features in a class. It is the option of the producer of a class to group and order the features in some fashion that has some meaning. Many years of Eiffel development experience are reflected in the classes in the Eiffel Base Library. This is a good place to look for examples of well constructed classes. }}
{{tip|There is not a technical requirement governing the grouping or ordering of features in a class. It is the option of the producer of a class to group and order the features in a fashion that holds some meaning. Many years of Eiffel development experience are reflected in the classes in the Eiffel Base Library. This is a good place to look for examples of well constructed classes. }}
===Invariant===

4
documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/using-referenced-assemblies.wiki
View File

@@ -5,11 +5,11 @@ Eiffel for.NET is a first class citizen in the Microsoft.NET programming world.
Being an Eiffel for.NET programmer obviously put you in a very powerful position. How do you take advantage of it?
To use.NET software components from Eiffel for.NET requires you to have some understanding of both.NET and Eiffel and how their respective object models differ. If you have read the rest of the help topics in [[Eiffel for.NET Language| this section]] then you have a pretty good idea of what the Eiffel method and language are all about.
To use.NET software components from Eiffel for.NET requires you to have some understanding of both.NET and Eiffel and how their respective object models differ. If you have read the rest of the help topics in [[Eiffel for .NET|this section]] then you have a pretty good idea of what the Eiffel method and language are all about.
When you begin to build software in Eiffel for.NET, you will likely find a need to reuse types from the.NET libraries. These libraries are called assemblies. When you reference a assembly using Eiffel for.NET, the types in the assembly become available to you in a form that makes them look like so many Eiffel classes. The names for types and members will conform to Eiffel conventions. The same thing happens when you are programming against assemblies in Visual Basic.NET or Visual C#.NET.
The section called [[Eiffel for .NET Conventions|Conventions]] covers the details the Eiffel conventions and how the.NET types are made available to Eiffel for.NET programmers.
The section called [[Conventions]] covers the details the Eiffel conventions and how the.NET types are made available to Eiffel for.NET programmers.