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

Author:halw

Browse Source 
Date:2009-11-11T05:07:08.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@353 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-11-11 05:07:08 +00:00
parent 8f8e5945df
commit 0cafe122f9
6 changed files with 26 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -172,6 +172,12 @@ Another not-so-obvious CAP is related to the use of the logical implication:
</code>
==The bottom line on CAPs==
In summary, CAPs provide void-safe protection for certain types of detachable expressions.
Possibly the characteristic of CAPs which is most important to developers is whether or not a particular CAP is supported by the compiler. In other words, if the compiler can provide assurance that a certain code pattern provides void-safe protection, then the developer has that pattern available as a CAP. Likewise, even if a pattern can be shown to be a CAP, but for some reason it is not supported by the compiler, then that pattern is not available as a CAP and the compiler will not allow its use.