diff options
| author | Serge Zaitsev <zaitsev.serge@gmail.com> | 2018-01-25 22:49:10 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-01-25 22:49:10 +0200 |
| commit | 6784c826d9674915a4d89649c6288e6aecb4110d (patch) | |
| tree | 4f9698183cea7b4cf9dcf55d7f4055ab96882303 | |
| parent | 35086597a72d94d8393e6a90b96e553d714085bd (diff) | |
| parent | f276e23a74f6a2f4342cf2094d99d869408512e9 (diff) | |
Merge pull request #123 from drbitboy/btc/typos
btc/typos - JSON_ERROR_... should be JSMN_ERROR_... in README.md
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -153,9 +153,9 @@ If something goes wrong, you will get an error. Error will be one of these: * `JSMN_ERROR_NOMEM` - not enough tokens, JSON string is too large * `JSMN_ERROR_PART` - JSON string is too short, expecting more JSON data -If you get `JSON_ERROR_NOMEM`, you can re-allocate more tokens and call +If you get `JSMN_ERROR_NOMEM`, you can re-allocate more tokens and call `jsmn_parse` once more. If you read json data from the stream, you can -periodically call `jsmn_parse` and check if return value is `JSON_ERROR_PART`. +periodically call `jsmn_parse` and check if return value is `JSMN_ERROR_PART`. You will get this error until you reach the end of JSON data. Other info |