Skip to content

Updated language use in cbmc-assertions.md #3534

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 5, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions doc/cprover-manual/cbmc-assertions.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,16 +4,16 @@

[Assertions](http://en.wikipedia.org/wiki/Assertion_%28computing%29) are
statements within the program that attempt to capture the programmer's
intent. The ANSI-C standard defines a header file
intent. The ANSI C standard defines a header file
[assert.h](http://en.wikipedia.org/wiki/Assert.h), which offers a macro
`assert(cond)`. When executing a statement such as
`assert(cond)`. When executing a statement such as:

```C
assert(p!=NULL);
```

the execution is aborted with an error message if the condition
evaluates to *false*, i.e., if `p` is NULL in the example above. The
evaluates to *false*, that is, if `p` is NULL in the example above. The
CPROVER tools can check the validity of the programmer-annotated
assertions statically. Specifically, the CPROVER tools will check that
the assertions hold for *any* nondeterministic choice that the program
Expand Down Expand Up @@ -49,7 +49,7 @@ if(i>=0 && i<100)
```

The nondeterministic choice will guess the element of the array that is
nonzero. The code fragment above is therefore equivalent to
nonzero. The code fragment above is therefore equivalent to:

```C
int a[100], i;
Expand Down