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

Author:halw

Browse Source 
Date:2009-05-21T16:56:26.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@224 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-05-21 16:56:26 +00:00
parent c04f788585
commit 760815367b
2 changed files with 21 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
documentation/current/method/void-safe-programming-eiffel/converting-existing-software-void-safety/index.wiki
View File

@@ -291,6 +291,18 @@ So the invariant clauses that we saw above would now become:
segment_traversal_convention: (segment_array.is_empty) = (not segment_readable) segment_traversal_convention: (segment_array.is_empty) = (not segment_readable)
</code> </code>
We already have compiler errors (VJAR's) that point us to those places in which we have code that sets either <code>sequence_array</code> or <code>segment_array</code> to <code>Void</code>. Like this:
<code>
segment_array := Void
</code>
These instances need to be changed to attach an empty array, maybe like this:
<code>
create segment_array.make (1, 0)
</code>
Additionally, some postconditions which reference the implementation features <code>sequence_array</code> and/or <code>segment_array</code> would have to be changed. Looking at the postcondition clauses for <code>segment_start</code> we see that <code>segment_array</code> is expected (or not) to be <code>Void</code>: Additionally, some postconditions which reference the implementation features <code>sequence_array</code> and/or <code>segment_array</code> would have to be changed. Looking at the postcondition clauses for <code>segment_start</code> we see that <code>segment_array</code> is expected (or not) to be <code>Void</code>:
<code> <code>
@@ -317,7 +329,6 @@ To support the "empty array" design, <code>segment_start</code>'s postcondition
===Using generic classes=== ===Using generic classes===
===Using '''check''' blocks===
==Transitioning steps== ==Transitioning steps==

2
documentation/current/method/void-safe-programming-eiffel/creating-new-void-safe-project.wiki
View File

@@ -54,7 +54,7 @@ This setting instructs the compiler to recheck inherited features in descendant
As of EiffelStudio version 6.4, the majority of the libraries distributed with EiffelStudio are void-safe. As of EiffelStudio version 6.4, the majority of the libraries distributed with EiffelStudio are void-safe.
During a period of transition, there will be different Eiffel configuration files (.ecf's) for non-void-safe and void-safe projects. If you have set the '''Void-safe''' setting to check for void-safety, then when you add a library to your project in EiffelStudio, you will see the void-safe configurations by default. After the transition period, it is expected that there will be only one version of the configuration files for each library. The single configuration files will serve both non-void-safe and void-safe projects. {{note|During a period of transition, there will be different Eiffel configuration files (.ecf's) for non-void-safe and void-safe projects (for example, base.ecf and base-safe.ecf). If you have set the '''Void-safe''' setting to check for void-safety, then when you add a library to your project in EiffelStudio, you will see only the void-safe configurations by default. After the transition period, it is expected that there will be only one version of each of the configuration files for each library. The single configuration files will serve both non-void-safe and void-safe projects. }}
==Using non-void-safe libraries== ==Using non-void-safe libraries==