v.help: document the new -force-bounds-checking option

This commit is contained in:
Delyan Angelov 2025-07-23 15:44:50 +03:00
parent 5c56909547
commit bf03add8eb
No known key found for this signature in database
GPG Key ID: 66886C0F12D595ED

View File

@ -112,6 +112,13 @@ NB: the build flags are shared with the run command too:
cases, it is preferable to not turn it off, than disable it, and have a program that may
do out of bounds accesses.
-force-bounds-checking
Programs compiled with this option, will *ALWAYS* do runtime checking of array access
operations, even inside functions/methods, that were tagged with `@[direct_array_access]`.
This allows for more convenient testing of modules that do use `@[direct_array_access]`,
extensively (like `math.big`), without constantly edititing their source code to remove/add
the tag. Note: this option overrides -no-bounds-checking .
-prof, -profile <file.txt>
Compile the executable with all functions profiled.
The profile results will be stored in `file.txt`.