trivial: s/f/f2/

mfwitten · mfwitten · commit c397543fdde7 · 2025-09-28T22:33:36.000-04:00
A comment in a code example was intended to refer to a function named "f2",
but the comment uses the name "f" instead, presumably because the code was
copied from the previous example; this commit fixes the typo.
diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md
@@ -767,7 +767,7 @@ We can of course pass the number of elements along with the pointer:
 
     void g2(int n)
     {
-        f2(new int[n], n);  // bad: a wrong number of elements can be passed to f()
+        f2(new int[n], n);  // bad: a wrong number of elements can be passed to f2()
     }
 
 Passing the number of elements as an argument is better (and far more common) than just passing the pointer and relying on some (unstated) convention for knowing or discovering the number of elements. However (as shown), a simple typo can introduce a serious error. The connection between the two arguments of `f2()` is conventional, rather than explicit.

Original file line number	Diff line number	Diff line change
`@@ -767,7 +767,7 @@ We can of course pass the number of elements along with the pointer:`
`767`	`767`
`768`	`768`	`void g2(int n)`
`769`	`769`	`{`
`770`		`- f2(new int[n], n); // bad: a wrong number of elements can be passed to f()`
	`770`	`+ f2(new int[n], n); // bad: a wrong number of elements can be passed to f2()`
`771`	`771`	`}`
`772`	`772`
`773`	`773`	Passing the number of elements as an argument is better (and far more common) than just passing the pointer and relying on some (unstated) convention for knowing or discovering the number of elements. However (as shown), a simple typo can introduce a serious error. The connection between the two arguments of `f2()` is conventional, rather than explicit.