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

Author:manus

Browse Source 
Date:2012-02-10T23:42:08.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1054 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2012-03-23 22:38:31 +00:00
parent 589a2fbe75
commit 2ed4cb67cf
2 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
documentation/current/eiffelstudio/eiffelstudio-reference/compiler/compiler-history/major-changes-between-ise-eiffel-68-and-ise-eiffel-70.wiki
View File

@@ -2,9 +2,6 @@
[[Property:link_title|7.0]] [[Property:link_title|7.0]]
[[Property:weight|13]] [[Property:weight|13]]
[[Property:uuid|0211321e-969d-04a4-66ee-2a6069836845]] [[Property:uuid|0211321e-969d-04a4-66ee-2a6069836845]]
{{UnderConstruction}}
==What's new== ==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 <e>{EXCEPTIONS}.die</e>. 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: * 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 <e>{EXCEPTIONS}.die</e>. 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:
<e> <e>

1
documentation/current/why-eiffel/eiffel-two-minute-fact-sheet.wiki
View File

@@ -50,6 +50,7 @@ Eiffel consists of:
***Includes multiple and repeated inheritance ***Includes multiple and repeated inheritance
***Safe and fully controllable ***Safe and fully controllable
**Genericity (generic classes), including constrained genericity **Genericity (generic classes), including constrained genericity
**Platform independent concurrency ([[Concurrent Eiffel with Scoop|SCOOP]])
*Widely recognized as simultaneously the simplest and most complete implementation of object-oriented concepts *Widely recognized as simultaneously the simplest and most complete implementation of object-oriented concepts
*Is clean, elegant, readable, easy to learn *Is clean, elegant, readable, easy to learn