Max Bruckner
|
d2d19127d3
|
cJSON_ConfigurationChangeParseEnd -> cJSON_ConfigurationGetParseEnd
This is probably a better approach than potentially having a pointer
that points to garbage on the stack and gets written to by cJSON.
|
2018-03-25 23:32:03 +02:00 |
|
Max Bruckner
|
691a83a479
|
cJSON_CreateConfig: Don't allow configuration, always use default
|
2018-03-25 23:32:03 +02:00 |
|
Max Bruckner
|
ae9dc3e7db
|
cJSON_ConfigurationChangeAllowDataAfterJson
|
2018-03-25 23:32:03 +02:00 |
|
Max Bruckner
|
eeaaaac63e
|
cJSON_ConfigurationChangeCaseSensitivity
|
2018-03-25 23:32:03 +02:00 |
|
Max Bruckner
|
78b5bed9a0
|
cJSON_ConfigurationChangeFormat
|
2018-03-25 23:32:03 +02:00 |
|
Max Bruckner
|
1a8f732749
|
cJSON_ConfigurationChangePrebufferSize
|
2018-03-25 23:32:03 +02:00 |
|
Max Bruckner
|
88c39fa2e4
|
cJSON_ConfigurationChangeParseEnd
Add a pointer to an end position of parsing to the cJSON_Configuration
object. (Essentially like return_parse_end, but as offset instead of
pointer).
|
2018-03-25 23:32:03 +02:00 |
|
Max Bruckner
|
9d801d64ea
|
cJSON_CreateConfiguration, cJSON_ConfigurationChange{Allocators,Userdata}
|
2018-03-25 23:32:03 +02:00 |
|