- 14 11月, 2016 5 次提交
-
-
由 Max Bruckner 提交于
Library names: libcJSON -> libcjson libcJSON_utils -> libcjson_utils
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
- 11 11月, 2016 1 次提交
-
-
由 Max Bruckner 提交于
-
- 08 11月, 2016 5 次提交
-
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
This reverts commit 3ea491c0.
-
- 07 11月, 2016 1 次提交
-
-
由 Max Bruckner 提交于
-
- 05 11月, 2016 1 次提交
-
-
由 Max Bruckner 提交于
Big thanks at mvollmer (https://sourceforge.net/p/cjson/bugs/45/)
-
- 04 11月, 2016 1 次提交
-
-
由 Max Bruckner 提交于
Do not always build static and dynamic
-
- 01 11月, 2016 1 次提交
-
-
由 Max Bruckner 提交于
ARM Compilation
-
- 31 10月, 2016 2 次提交
-
-
由 Max Bruckner 提交于
don't ignore malloc failure in cJSON_PrintBuffered
-
由 Rod Vagg 提交于
-
- 30 10月, 2016 1 次提交
-
-
由 Fabrice Fontaine 提交于
Currently, the static and dynamic version of the libraries are always built as add_library is called twice. Instead, this patch will use the standard CMake variable BUILD_SHARED_LIBS to know if the static or the dynamic version must be built. Signed-off-by: NFabrice Fontaine <fabrice.fontaine@orange.com>
-
- 29 10月, 2016 16 次提交
-
-
由 Max Bruckner 提交于
Reformat cJSON_Utils.c and test.c
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
NOTE: This can change the assembly slightly, in my case it reordered two instructions. This is due to the change from: which = (10 * which) + *pointer++ - '0'; to which = (10 * which) + (*pointer++ - '0'); This means that after the change, the subtraction runs before the addition instead of after that. That shouldn't change the behavior though.
-
- 28 10月, 2016 2 次提交
-
-
由 Max Bruckner 提交于
Remove redundant test from cJSON_AddItemToArray
-
由 Jonathan Fether 提交于
The test for whether "c" is null is redundant. Since this is the else case of "(!c)", and the only way "c" is changed is by the instruction assigning it "c->next" on the condition here, simply verifying that "c->next" isn't null is sufficient.
-
- 18 10月, 2016 1 次提交
-
-
由 Ian Mobley 提交于
-
- 14 10月, 2016 3 次提交
-
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-
由 Max Bruckner 提交于
-