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

Update wikipage Converting existing software to void-safety. (Signed-off-by:alexk).

Browse Source 
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1716 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
eiffel-org
2016-12-26 11:19:22 +00:00
parent 649f63e883
commit 5e84982b0e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/trunk/eiffel/Language_reference/void-safe-programming-eiffel/converting-existing-software-void-safety/index.wiki
View File

@@ -76,7 +76,7 @@ So, fix any problems that arise out of turning on full class checking.
The second step in conversion of existing software is to change the values of the other void-safe related project settings and use the void-safe configurations for any delivered libraries and precompilations.
In the project settings for the target in which you are working, set '''Void-safe''' to either '''Complete''', '''Initialization''' or '''Conformance'''.
In the project settings for the target in which you are working, set '''Void safety''' to '''Complete''', '''Transitional''' , '''Initialization''' or '''Conformance'''.
{{note|Remember that during a transitional period starting with v6.4, there will be multiple versions of the configuration files for Eiffel libraries and precompiles. For example, base.ecf (void-unsafe) and base-safe.ecf (void-safe). Starting with v16.11 there is only one configuration file for libraries (e.g., base.ecf) that works with both void-safe and void-unsafe client software, but if you are using a precompile, there could be different versions for void-safe and void-unsafe precompiles.}}