mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2026-02-07 19:14:39 +01:00
Code Issues Packages Projects Releases Wiki Activity

Author:halw

Browse Source 
Date:2012-08-24T03:19:27.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1170 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2012-08-27 12:18:28 +00:00
parent 4c9cad6262
commit eb5d774880
2 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/current/method/eiffel-tutorial-et/et-inheritance.wiki
View File

@@ -583,7 +583,7 @@ feature
</code>
Again what counts, to determine if there is an invalid name clash, is the final name of the features. In this example to of the joined features were originally called <code>f</code>; the one from <code>A</code> was called <code>g</code>, but in <code>D</code> it is renamed as <code>f</code>, so without the undefinition it would cause an invalid name clash.
Again what counts, to determine if there is an invalid name clash, is the final name of the features. In this example, two of the joined features were originally called <code>f</code>; the one from <code>A</code> was called <code>g</code>, but in <code>D</code> it is renamed as <code>f</code>, so without the undefinition it would cause an invalid name clash.
Feature joining is the most common application of uneffecting. In some non-joining cases, however, it may be useful to forget the original implementation of a feature and let it start a new life devoid of any burden from the past.