From b163af420070d3ef9f9bd0a8fb8dcb35dcdcdd73 Mon Sep 17 00:00:00 2001 From: halw Date: Mon, 20 Aug 2012 14:03:48 +0000 Subject: [PATCH] Initiative to replace "Eiffel language" and similar with "Eiffel programming language" Author:halw Date:2012-08-20T14:03:48.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1133 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../current/method/eiffel-tutorial-et/et-inheritance.wiki | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/documentation/current/method/eiffel-tutorial-et/et-inheritance.wiki b/documentation/current/method/eiffel-tutorial-et/et-inheritance.wiki index 400c0bd5..e6ab1d04 100644 --- a/documentation/current/method/eiffel-tutorial-et/et-inheritance.wiki +++ b/documentation/current/method/eiffel-tutorial-et/et-inheritance.wiki @@ -1054,7 +1054,7 @@ inherit {NONE} Here there are two inherit clauses, one to specify conforming parents, and one to specify non-conforming parents. The clause specifying the conforming inheritance must precede the one specifying the non-conforming inheritance. -{{note|According to the Eiffel language standard, it is possible to have any number of inherit clauses an any order, however EiffelStudio versions as late as 6.5 allow only one conforming and one non-conforming clause, with the conforming clause preceding the non-conforming one. This restriction will be removed in a future release.}} +{{note|According to the Eiffel programming language [http://www.ecma-international.org/publications/standards/Ecma-367.htm standard], it is possible to have any number of inherit clauses an any order, however EiffelStudio versions as late as 6.5 allow only one conforming and one non-conforming clause, with the conforming clause preceding the non-conforming one. This restriction will be removed in a future release.}} So, in this case, at runtime it is valid for a direct instance of MY_HEIR_CLASS to be attached to an entity of type MY_CONFORMING_PARENT, but not to an entity of type MY_NON_CONFORMING_PARENT. Accordingly, the compiler would reject any code in which an instance of MY_HEIR_CLASS could become attached to an entity of type MY_NON_CONFORMING_PARENT. Because the polymorphic attachment cannot be made, the possibility of a catcall is avoided. @@ -1064,4 +1064,3 @@ So, in this case, at runtime it is valid for a direct instance of MY_HEIR_ -