Skip to content

Commit 57c8f51

Browse files
committed
C++: Address docs review comments
1 parent 3f905f2 commit 57c8f51

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/codeql/codeql-language-guides/analyzing-data-flow-in-cpp-new.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22

33
.. pull-quote:: Note
44

5-
The data flow library described here is available from CodeQL 2.13.0 onwards. See :ref:`here <analyzing-data-flow-in-cpp>` for the library available in earlier versions.
5+
The data flow library described here is available from CodeQL 2.12.5 onwards. See :ref:`here <analyzing-data-flow-in-cpp>` for the library available in earlier versions.
66

77
Analyzing data flow in C and C++ (New)
8-
================================
8+
======================================
99

1010
You can use data flow analysis to track the flow of potentially malicious or insecure data that can cause vulnerabilities in your codebase.
1111

@@ -101,7 +101,7 @@ The following query finds the filename passed to ``fopen``:
101101
fc.getTarget() = fopen
102102
select fc.getArgument(0)
103103
104-
Unfortunately, this will only give the expression in the argument, not the values which could be passed to it. So we use local data flow to find all expressions that flow into the argument, where we use ``asIndirectExpr(1)`` as we are interested in the value of the string passed to `fopen`, not the pointer pointing to it:
104+
However, this will only give the expression in the argument, not the values which could be passed to it. Instead we can use local data flow to find all expressions that flow into the argument, where we use ``asIndirectExpr(1)``. This is because we are interested in the value of the string passed to `fopen`, not the pointer pointing to it:
105105

106106
.. code-block:: ql
107107

0 commit comments

Comments
 (0)