| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
similar to secp256k1 include and compile univalue over a subtree
|
| |
|
|
|
|
| |
Fix https://github.com/bitcoin/bitcoin/issues/6558. In particular, stop
parsing JSON after the first object or array is finished. Check that no
other garbage follows, and fail the parser if it does.
|
| |
|
|
|
|
|
|
|
|
| |
JSON makes no distinction between numbers and reals, and our code
doesn't need to do so either.
This removes VREAL, as well as its specific post-processing in
`UniValue::write`. Non-monetary amounts do not need to be forcibly
formatted with 8 decimals, so the extra roundtrip was unnecessary
(and potentially loses precision).
|
| | |
|
| |
|
|
|
|
| |
Univalue's parsing of \u escape sequences did not handle NUL characters
correctly. They were, effectively, dropped. The extended test-case
fails with the old code, and is fixed with this patch.
|
| | |
|
| |
|
|
| |
- avoid breaking the API because of different number/percision handling
|
| | |
|
| |
|
|
|
|
|
|
| |
Make sure that chainparams and logging is properly initialized. Doing
this for every test may be overkill, but this initialization is so
simple that that does not matter.
This should fix the travis issues.
|
| | |
|
| | |
|
| |
|