doc: use new block_to_connect parameter name
What the developer wrote
Authored by stickies-v
doc: use new block_to_connect parameter name
This was previously changed in 9ba1fff29e4794615c599e59ef453848a9bdb880,
without updating the documentation.
Co-authored-by: stringintech <stringintech@gmail.com>
What changed, and why it matters
This is a one-word documentation fix inside a code comment. A function parameter was renamed from 'pblock' to 'block_to_connect' in an earlier commit, and this change simply updates the surrounding comment to match. It does not alter any executable code, behavior, or security property.
No security action needed. This is a routine documentation-only cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit changes a single line in src/validation.cpp: the Doxygen-style comment for the block connection logic is updated to use the current parameter name ‘block_to_connect’ instead of the old name ‘pblock’. No logic, control flow, data handling, or validation rules are modified.
Changed components
src/validation.cpp (documentation comment only)Inspect captured patch +1 / −1
diff --git a/src/validation.cpp b/src/validation.cpp
index 46265a19..8fcc719a 100644
--- a/src/validation.cpp
+++ b/src/validation.cpp
@@ -3103,7 +3103,7 @@ public:
};
/**
- * Connect a new block to m_chain. pblock is either nullptr or a pointer to a CBlock
+ * Connect a new block to m_chain. block_to_connect is either nullptr or a pointer to a CBlock
* corresponding to pindexNew, to bypass loading it again from disk.
*
* The block is added to connectTrace if connection succeeds.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.