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:halw

Browse Source 
Date:2009-05-30T17:27:25.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@231 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-05-30 17:27:25 +00:00
parent b82d853640
commit b4cb3277f0
3 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -9,11 +9,11 @@ These pages are the central repository of information about Eiffel and the produ
The documentation is organized into virtual books. Each book covers an important aspect of the world of Eiffel.
* [[Guide]] -- Guide to Eiffel Information
* [[Why Eiffel?]] -- Why Eiffel?
* [[Method|Method and Language]] -- The Eiffel Method and Language
* [[EiffelStudio]] -- The EiffelStudio Interactive Development Environment
* [[Solutions]] -- Eiffel Solutions, Technologies, and Class Libraries
* [[Platform specifics]] -- Specific support for particular platforms, e.g., Microsoft Windows
* [[Method|Method and Language]] -- The Eiffel Method and Language
* [[Why Eiffel?]] -- Why Eiffel?
* [[Community]] -- Community Contributions
<!--break-->
Sources of information on Eiffel include:
@@ -25,14 +25,6 @@ Sources of information on Eiffel include:
:You are reading this book now.
===[[Why Eiffel?]] -- Why Eiffel? ===
:A summary of the arguments for using Eiffel.
===[[Method|Method and Language]] -- The Eiffel Method and Language===
:Materials promoting the understanding of the Eiffel software development method and Eiffel the language.
===[[EiffelStudio]] -- The EiffelStudio Interactive Development Environment===
:Information about installing and using EiffelStudio
@@ -45,6 +37,14 @@ Sources of information on Eiffel include:
:Although most Eiffel technology is completely platform-independent, Eiffel also provides important platform-specific solutions, described in this book.
===[[Method|Method and Language]] -- The Eiffel Method and Language===
:Materials promoting the understanding of the Eiffel software development method and Eiffel the language.
===[[Why Eiffel?]] -- Why Eiffel? ===
:A summary of the arguments for using Eiffel.
===[[Community]] -- You can contribute to the documentation!===
:EiffelStudio documentation is available in a convenient Wiki format. This makes it possible to improve the documentation continuously and make sure it is always up to date.

2
documentation/current/method/index.wiki
View File

@@ -10,6 +10,6 @@ At the heart of the Eiffel Development Framework is the Eiffel method. Everythin
In order for us to communicate effectively about the activities of the method we must have some way to record the products of those activities. That is what Eiffel the language does for us ... with the added benefit that, ultimately, we implement whole running software systems in the language.
The method is laid out in wonderful detail in [http://www.eiffel.com/doc/oosc/ Object-oriented Software Construction, 2nd Edition]. But, if you're just getting started, you will find some good introductory material on this page. The invitation to Eiffel is fairly short introduction to the method and language. and the tutorial gives a more detailed look.
The method is laid out in wonderful detail in [http://www.eiffel.com/doc/oosc/page.html Object-oriented Software Construction, 2nd Edition]. But, if you're just getting started, you will find some good introductory material on this page. The invitation to Eiffel is fairly short introduction to the method and language. and the tutorial gives a more detailed look.

2
documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/genericity.wiki
View File

@@ -72,7 +72,7 @@ This is because "item" is type <code>ANY</code> and although it may be currently
You can see that this type of list has its drawbacks. Of course you could build a <code>LIST_OF_CATS</code> class in which <code>item</code> and the argument for <code>put</code> would be of type <code>CAT</code>. This would let you <code>purr</code> a cat without pulling it out of the list, and it would also prevent you from accidently letting old Thor in with the cats. But, every time you needed a list to hold a different type of object, you have to write a new class.
Indeed, this is how things are done in environements without facilities genericity.
Indeed, this is how things are done in environments without facilities genericity.
What we would like to have is a way to produce the text of the list class once. Then only when we make declarations do we add the additional information about the particular types we want allowed in the list.