- 11 3月, 2021 1 次提交
-
-
由 mamingshuai 提交于
-
- 09 9月, 2020 1 次提交
-
-
由 wenjun 提交于
-
- 29 7月, 2016 1 次提交
-
-
由 linghuazaii 提交于
-
- 28 7月, 2016 1 次提交
-
-
由 linghuazaii 提交于
Change iniparser_getint64(...) to iniparset_getlongint(...) and add unittest for iniparser_getlongint(...) and also add interface for longint equal in CuTest.h/CuTest.c.
-
- 27 7月, 2016 2 次提交
-
-
由 linghuazaii 提交于
-
由 linghuazaii 提交于
-
- 28 6月, 2016 1 次提交
-
-
由 Emmanuel Leblond 提交于
-
- 17 5月, 2015 2 次提交
-
-
由 Emmanuel Leblond 提交于
-
由 Emmanuel Leblond 提交于
-
- 28 4月, 2012 1 次提交
-
-
由 Kevin Pyle 提交于
The documentation disclaims support for building with a C++ compiler, so it is reasonable to assume that the library will be built with a plain C compiler, so the functions will all have plain C linkage. By default, a C++ application that wished to use libiniparser would need to wrap the inclusion of libiniparser headers in 'extern "C" { ... }' to reflect the C linkage of libiniparser. Instead, place that marker directly in the libiniparser headers, so that client applications do not need to care. This has no effect on normal compilation of libiniparser, since the new markers are inside a '#ifdef __cplusplus' guard, and straight C compilers do not define __cplusplus.
-
- 08 4月, 2012 1 次提交
-
-
由 Nicolas D 提交于
-
- 04 4月, 2012 1 次提交
-
-
由 Andrey Mazo 提交于
-
- 10 7月, 2011 1 次提交
-
-
由 James Spencer 提交于
-
- 09 7月, 2011 1 次提交
-
-
由 James Spencer 提交于
-
- 04 4月, 2011 1 次提交
-
-
由 ndevilla 提交于
-
- 03 3月, 2011 1 次提交
-
-
由 ndevilla 提交于
-
- 20 8月, 2010 1 次提交
-
-
由 Nicolas Devillard 提交于
-