hohn/codeql
1
0
Fork 0
mirror of https://github.com/github/codeql.git synced 2026-04-25 16:55:19 +02:00
Code Issues Packages Projects Releases Wiki Activity

C++: Stick to the pointer vs. indirection terminology.

Browse Source
This commit is contained in:
Mathias Vorreiter Pedersen
2023-10-18 13:47:09 +01:00
parent f6b1d66167
commit 44e214b933
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

@@ -187,7 +187,7 @@ Notice how the ``isSource`` and ``isSink`` are as expected: we're looking for fl
In a real query the ``isAdditionalFlowStep`` step would be restricted in various ways to make sure that it doesn't add too much flow (since flow from a field qualifier to the field access in general will generate a lot of spurious flow). For example, one could restrict ``fa`` to be a field access that targets a particular field, or a field access of a field that's defined in a certain ``struct`` type.
We have an important choice here: Should the relationship between ``n2`` and ``fa`` be implemented using ``asExpr`` or ``asIndirectExpr``?
We have an important choice here: Should ``n2`` be the node corresponding to the pointer value of ``fa`` or the indirection of ``fa`` (i.e., what ``fa`` points to)?
.. _using-asIndirectExpr: