 Max Bruckner
|
a0aa2df75a
|
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-02-03 16:42:58 +01:00 |
|
|
Max Bruckner
|
ba81437601
|
cJSON_CreateConfig: Don't allow configuration, always use default
|
2018-02-03 16:42:58 +01:00 |
|
|
Max Bruckner
|
d664199036
|
cJSON_ConfigurationChangeAllowDataAfterJson
|
2018-02-03 16:42:58 +01:00 |
|
|
Max Bruckner
|
7e4ac634c6
|
cJSON_ConfigurationChangeCaseSensitivity
|
2018-02-03 16:42:57 +01:00 |
|
|
Max Bruckner
|
1d9d2e8673
|
cJSON_ConfigurationChangeFormat
|
2018-02-03 16:42:57 +01:00 |
|
|
Max Bruckner
|
c4c52cfe58
|
cJSON_ConfigurationChangePrebufferSize
|
2018-02-03 16:42:57 +01:00 |
|
|
Max Bruckner
|
0474d4d85f
|
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-02-03 16:42:56 +01:00 |
|
|
Max Bruckner
|
95d333b5cf
|
cJSON_CreateConfiguration, cJSON_ConfigurationChange{Allocators,Userdata}
|
2018-02-03 16:42:56 +01:00 |
|