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

m

Browse Source 
Author:halw
Date:2011-10-13T21:31:58.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@997 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2011-10-13 21:31:58 +00:00
parent 0bf0dc7c63
commit 09bbeb2d09
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/current/method/void-safe-programming-eiffel/converting-existing-software-void-safety/mixing-void-safe-and-void-unsafe-software.wiki
View File

@@ -12,7 +12,7 @@ Under some circumstances it is possible and even helpful to mix void-safe and vo
=Rule for mixing void-safety modes=
The rule for using void-safe and void-unsafe software together are fairly simple.
The rule for using void-safe and void-unsafe software together is fairly simple.
{{Rule|name=Mixing void-safe and void-unsafe software|text=<br/>
@@ -20,7 +20,7 @@ The rule for using void-safe and void-unsafe software together are fairly simple
2) A class that is void-safe may depend only upon other classes that are void-safe.}}
This means that if the root class of system is void-safe, then every other class in the system must also be void-safe.
This means that if the root class of a system is void-safe, then every other class in the system must also be void-safe.
However, if you are converting a system to void-safety, it's likely that your root class and the classes in the closely related clusters will be void-unsafe. The rule allows you to mix the void-safe versions of the Eiffel Software library classes from the EiffelStudio distribution with your void-unsafe system during conversion.