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:bmeyer

Browse Source 
Date:2009-08-04T19:24:46.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@276 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
bmeyer
2009-08-04 19:25:25 +00:00
parent fdb16970dc
commit 18d1686066
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
documentation/current/papers/void-safety-how-eiffel-removes-null-pointer-dereferencing.wiki
View File

@@ -1,10 +1,12 @@
[[Property:title|Void safety: how Eiffel removes void references]]
[[Property:title|Void safety: how Eiffel removes null-pointer dereferencing]]
[[Property:link_title|Void-safety: how Eiffel removes null-pointer dereferencing]]
[[Property:weight|0]]
[[Property:uuid|d9380464-4312-b76e-9bfd-e57df0f59b4a]]
This white paper (see link below) presents the Eiffel void safety mechanism, fully implemented in EiffelStudio 6.4.
This white paper (see "Attachment" link below) presents the Eiffel void safety mechanism, fully implemented in EiffelStudio 6.4.
In almost every program running today there is a ticking time bomb: the risk of a "void call". A void call is possible in programs written in almost any programming language; its effect is usually to crash the program. Many unexplained program crashes and other abnormal behaviors result from void calls. While extensive testing can decrease the likelihood of a void call, it cannot remove the possibility. The solution has to com from the programming language.
In almost every program running today there is a ticking time bomb: the risk of a "void call". A void call is possible in programs written in almost any programming language; its effect is usually to crash the program. Many unexplained program failures and other abnormal behaviors result from void calls.
While extensive testing can decrease the likelihood of a void call, it cannot remove the possibility. The solution has to com from the programming language.
<!--break-->
Professor C.A.R. Hoare from Microsoft Research, winner of the Turing Award and the Kyoto Prize, calls the presence of void calls in modern programming languages the "billion-dollar mistake":