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

Author:halw

Browse Source 
Date:2009-11-23T23:00:29.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@363 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-11-23 23:00:29 +00:00
parent e1e03f95b1
commit 22b0780a3a
2 changed files with 29 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
documentation/current/method/void-safe-programming-eiffel/what-makes-certified-attachment-pattern.wiki
View File

@@ -12,7 +12,7 @@ Certified Attachment Patterns (CAPs) were described in the section on [[Void-saf
A simple example is the familiar test for void reference:
<code>
if l_x /= Void then
l_x.do_something
l_x.do_something -- Valid for formal arguments, local variables, and stable attributes
end
</code>
We know that after the explicit check to make sure <code>l_x</code> is not <code>Void</code>, that the feature application <code>l_x.do_something</code> is void-safe.
@@ -105,7 +105,7 @@ But, if <code>l_string</code> had been a target of an assignment in which the so
if l_string /= Void then
l_string.append ("abc") -- Valid
l_string := my_detachable_string
l_string.append ("xyz") -- Invalid: my_detachable_string could be void
l_string.append ("xyz") -- Invalid: my_detachable_string might have been void
...
</code>
@@ -119,7 +119,7 @@ We've already seen the simple test for void as a CAP:
...
if l_str /= Void then
l_str.append ("xyz")
l_str.append ("xyz") -- Valid
end
</code>
@@ -129,7 +129,7 @@ Additionally, a creation instruction can serve as a CAP. After the execution of
l_str: detachable STRING
do
create l_str.make_empty
l_str.append ("xyz")
l_str.append ("xyz") -- Valid
...
</code>