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

Minor reorganization of contents. From developer feedback.

Browse Source 
Author:halw
Date:2011-11-28T16:51:13.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1029 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2011-11-28 16:51:13 +00:00
parent 0a582b350d
commit 86d76d04de
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/void-safety-background-definition-and-tools.wiki
View File

@@ -28,7 +28,7 @@ Of course this is not an issue with instances of expanded types, because these i
So, references are necessary, but we want them to be trouble free.
=Void-safe software=
==Void-safe software==
Void-safe software, then, is software in which the compiler can give assurance, through a static analysis of the code, that at run time whenever a feature is applied to a reference, that the reference in question will have an object attached. This means that the feature call
<code>
@@ -42,7 +42,7 @@ is valid only if we are assured that <code>x</code> will be attached to an objec
Once we have committed ourselves to this validity rule, we must have a strategy for complying with the rule.
==Elements of the void-safe strategy==
=Elements of the void-safe strategy=
Here are the tools of void-safe trade. They will each be addressed in more detail throughout the documentation that follows. As you look at these elements it helps to try to think about things from the compiler's viewpoint ... after all, it is the compiler that we expect to give us the guarantee that our code is indeed void-safe.