mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-07 07:12:25 +01:00
Author:manus
Date:2014-03-03T19:11:30.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1274 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -1,8 +1,7 @@
|
||||
[[Property:title|Void safety: how Eiffel removes null-pointer dereferencing]]
|
||||
[[Property:link_title|Void-safety: how Eiffel removes null-pointer dereferencing]]
|
||||
[[Property:title|Void-safety: how Eiffel removes null-pointer dereferencing]]
|
||||
[[Property:weight|0]]
|
||||
[[Property:uuid|d9380464-4312-b76e-9bfd-e57df0f59b4a]]
|
||||
This white paper (see [[file:void-safe-eiffel.pdf|"Attachment" link ]] below) presents the Eiffel void safety mechanism, fully implemented in EiffelStudio 6.4.
|
||||
This white paper (see [[file:void-safe-eiffel.pdf|"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 failures and other abnormal behaviors result from void calls.
|
||||
|
||||
@@ -26,5 +25,5 @@ The Eiffel solution relies on a combination of language mechanisms:
|
||||
<li>The "Object Test" instruction lets programmers treat void values in a special way.
|
||||
</ul>
|
||||
|
||||
The White Paper (see the link below) describes the theoretical and practical challenges of ensuring void safety and presents the Eiffel mechanism.
|
||||
The White Paper (see the link below) describes the theoretical and practical challenges of ensuring void-safety and presents the Eiffel mechanism.-
|
||||
|
||||
|
||||
Reference in New Issue
Block a user