hohn/codeql
1
0
Fork 0
mirror of https://github.com/github/codeql.git synced 2026-04-26 09:15:12 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update docs/codeql/codeql-language-guides/advanced-dataflow-scenarios-cpp.rst

Browse Source
This commit is contained in:
Mathias Vorreiter Pedersen
2023-10-18 14:08:20 +02:00
committed by GitHub
parent b71248face
commit 59b26c0dad
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/codeql/codeql-language-guides/advanced-dataflow-scenarios-cpp.rst
View File

@@ -18,7 +18,7 @@ However, when a write to a field is not visible to CodeQL (for example, because
When you write additional flow steps to track pointers, you must decide whether the dataflow step should flow from the pointer or its indirection. Similarly, you must decide whether the additional step should target a pointer or its indirection.
In the dual situation where a read of a field is not visible to CodeQL, the dataflow library's "implicit read" mechanism can be used to achieve the right flow.
In contrast, if the read of a field is not visible to CodeQL, you can add an ``allowImplicitRead`` predicate to model the data flow.
The setup
---------