Author:halw

Date:2012-11-08T22:44:53.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1199 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2012-11-20 17:50:55 +00:00
parent f8bc1261bc
commit b0f62baecb
3 changed files with 9 additions and 2 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

View File

@@ -0,0 +1,3 @@
title=assertion-options
author=halw
path=content/assertion-options

View File

@@ -1,11 +1,15 @@
[[Property:title|Assertion Options]]
[[Property:weight|2]]
[[Property:uuid|12520e45-beb4-2200-9e60-91736a3ed092]]
This is where you can configure the assertion level for your project.
'''Assertions''' allows you to configure the assertion checking levels for your project. This means that any assertion type marked '''True''' in the '''Assertions''' table will be checked at runtime. So, in the example screen shown below, only preconditions (denoted in the table by '''Require''') will be checked at runtime. All other assertion types will not be checked at runtime.
Each assertion setting can be configured independently of the others.
'''Supplier Precondition''' is a special case. When you develop new software, your software reuses libraries of existing software from other sources, such as the Eiffel Libraries. This library software is often well-established and highly reliable. Setting '''Supplier Precondition''' to '''True''' is a convenient way of setting only precondition checking on libraries, while allowing your own software to be checked to whatever degree you've determined by adjusting the other assertion level settings.
[[Image:assertion-options|Condition dialog]]
Each precondition setting can be changed independently from each other.