You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,8 +35,8 @@ preprocessor ASSERTIONS to non-zero, eg:
35
35
```
36
36
fpm build --flag "-DASSERTIONS"
37
37
```
38
-
The program [example/invoke-via-macro.F90] demonstrates the preferred way to invoke the `assert` subroutine via the three provided macros.
39
-
Invoking `assert` this way insures that `assert` invocations will be completely removed whenever the `ASSERTIONS` macro is undefined (or defined to zero) during compilation.
38
+
The program [example/invoke-via-macro.F90] demonstrates the preferred way to invoke assertions via the three provided macros.
39
+
Invoking assertions this way ensures such calls will be completely removed whenever the `ASSERTIONS` macro is undefined (or defined to zero) during compilation.
40
40
Due to a limitation of `fpm`, this approach works best if the project using Assert is also a `fpm` project.
41
41
If instead `fpm install` is used, then either the user must copy `include/assert_macros.h` to the installation directory (default: `~/.local/include`) or
42
42
the user must invoke `assert` directly (via `call assert(...)`).
0 commit comments