Indices are used to index into the stack and to be compared with the stack size. Even though we don't expect the stack to a billions of elements big, it is correct to use size_t here.
Details
Details
- Reviewers
markblundeberg - Group Reviewers
Restricted Project - Commits
- rSTAGING655416f9d8cd: Use size_t for stack index in OP_MULTISIG
rABC655416f9d8cd: Use size_t for stack index in OP_MULTISIG
make check ./test/functional/test_runner.py
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
src/script/interpreter.cpp | ||
---|---|---|
1013 ↗ | (On Diff #10224) | Should k also be a size_t? I had to dig through some C++ standards to convince myself why stacktop(-isig - k) works now, when isig is size_t and k is an int... |
src/script/interpreter.cpp | ||
---|---|---|
1013 ↗ | (On Diff #10224) | No k iterate through 0 to CScriptNum, which are integers. |