aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2016-06-08 10:23:25 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2016-06-08 10:28:51 +0200
commite012f3cea0ca4096dd4dd59a356a973c43651912 (patch)
tree2d6b478372ca006337efe387ad9f6818caec56d3 /doc
parent0f24eaf253abe7d1479777ef10f8f4e8eeb9d06e (diff)
downloadbitcoin-e012f3cea0ca4096dd4dd59a356a973c43651912.tar.xz
util: Add ParseUInt32 and ParseUInt64
Add error and range-checking parsers for unsigned 32 and 64 bit numbers. The 32-bit variant is required for parsing sequence numbers from the command line in `bitcoin-tx` (see #8164 for discussion). I've thrown in the 64-bit variant as a bonus, as I'm sure it will be needed at some point. Also adds tests, and updates `developer-notes.md`.
Diffstat (limited to 'doc')
-rw-r--r--doc/developer-notes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/developer-notes.md b/doc/developer-notes.md
index add2fb5004..e40b73ffa7 100644
--- a/doc/developer-notes.md
+++ b/doc/developer-notes.md
@@ -323,7 +323,7 @@ Strings and formatting
buffer overflows and surprises with `\0` characters. Also some C string manipulations
tend to act differently depending on platform, or even the user locale
-- Use `ParseInt32`, `ParseInt64`, `ParseDouble` from `utilstrencodings.h` for number parsing
+- Use `ParseInt32`, `ParseInt64`, `ParseUInt32`, `ParseUInt64`, `ParseDouble` from `utilstrencodings.h` for number parsing
- *Rationale*: These functions do overflow checking, and avoid pesky locale issues