- 08 4月, 2019 1 次提交
-
-
由 Fabian Zahn 提交于
Used sizeof() operator for pointer increments and substituted sizeof() operator for the unsigned int mask calculation to "UNITY_INT_WIDTH / 8" in function "UnityAssertEqualIntArray".
-
- 12 3月, 2019 1 次提交
-
-
由 Alexander Brevig 提交于
-
- 31 1月, 2019 1 次提交
-
-
由 Fabian Zahn 提交于
-
- 25 1月, 2019 3 次提交
-
-
由 Luca Boccassi 提交于
Avoid declaring the loop variable inside the for statement to keep compatibility with c90: unity.c:1408: error: for' loop initial declaration used outside C99 mode
-
由 Fabian Zahn 提交于
-
由 Fabian Zahn 提交于
Macro UNITY_EXCLUDE_PRINT_FORMATTED changed to UNITY_INCLUDE_PRINT_FORMATTED. Enable printf via "-DUNITY_INCLUDE_PRINT_FORMATTED" compiler option.
-
- 29 11月, 2018 2 次提交
-
-
由 John Lindgren 提交于
-
由 John Lindgren 提交于
Negating the most-negative signed integer results in overflow, which is undefined behavior. Fix this by casting to an unsigned type first (unsigned overflow is well-defined as it uses modular arithmetic).
-
- 31 10月, 2018 3 次提交
- 28 10月, 2018 1 次提交
-
-
由 Fabian Zahn 提交于
-
- 27 10月, 2018 1 次提交
-
-
由 Fabian Zahn 提交于
-
- 19 10月, 2018 1 次提交
-
-
由 Levin Messing 提交于
-
- 14 10月, 2018 1 次提交
-
-
由 Fabian Zahn 提交于
Added include of 'stddef.h' to 'unity_internals.h' if 'UNITY_EXCLUDE_STDDEF_H' is not defined. This adds compiler independent support for the 'NULL' macro.
-
- 12 9月, 2018 1 次提交
-
-
由 Kyle Krueger 提交于
-
- 29 7月, 2018 1 次提交
-
-
由 elliot 提交于
-
- 26 7月, 2018 1 次提交
-
-
由 Roland Stahn 提交于
Macros TEST_ASSERT_LESS_OR_EQUAL_HEX32_MESSAGE() and TEST_ASSERT_LESS_OR_EQUAL_HEX64_MESSAGE() need to be mapped to UNITY_TEST_ASSERT_SMALLER_OR_EQUAL_HEXnn() instead of UNITY_TEST_ASSERT_SMALLER_THAN_HEXnn()
-
- 18 7月, 2018 1 次提交
-
-
由 Xenoamor 提交于
Flush the unity stdout buffer before calling TEST_ABORT(). This is because if TEST_PROTECT() has not previously been called this will cause a segmentation fault and the stdout buffer will fail to print Although the segmentation fault will still occur, the error that caused it will at least be displayed
-
- 18 2月, 2018 1 次提交
-
-
由 Fabian Zahn 提交于
-
- 11 2月, 2018 2 次提交
-
-
由 Jeremy Hannon 提交于
MISRA 2004 rule 19.10: inside macros, surround each parameter usage with parentheses.
-
由 Jeremy Hannon 提交于
parameter names should match between declaration and definition. (MISRA 2004 rule 16.4)
-
- 23 11月, 2017 1 次提交
-
-
由 Shreyas Balakrishna 提交于
-
- 08 11月, 2017 4 次提交
-
-
由 John Lindgren 提交于
-
由 John Lindgren 提交于
-
由 John Lindgren 提交于
-
由 John Lindgren 提交于
-
- 01 11月, 2017 1 次提交
-
-
由 John Lindgren 提交于
-
- 31 10月, 2017 1 次提交
-
-
由 Kate Hart 提交于
-
- 24 10月, 2017 1 次提交
-
-
由 Victor Lambret 提交于
Help error detection by adding specific colors for test results. This behavior is activated only when unity if compiled with UNITY_COLOR flag.
-
- 09 10月, 2017 2 次提交
-
-
由 John Lindgren 提交于
- Enable support for Green Hills Software compiler - Define weak implementations only once except on Windows
-
由 John Lindgren 提交于
MinGW supports a limited form of weak symbols, with the restriction that weak/default implementations need to be defined in the same translation unit they are called from. Strong/overriding symbols may of course be specified in a different translation unit.
-
- 21 9月, 2017 3 次提交
- 14 9月, 2017 1 次提交
-
-
由 John Lindgren 提交于
This is simpler and more flexible than embedding C code in the Ruby options (:suite_setup and :suite_teardown). However, support for :suite_setup and :suite_teardown is kept for backwards compatibility. Several configurations are possible: 1. :suite_setup and :suite_teardown options provided and used. 2. :suite_setup and :suite_teardown options not provided (nil): 2a. Weak symbols not supported; suiteSetUp() and suiteTearDown() are not called. It would be simpler to make user-provided functions mandatory in this case, but it could break some pre-existing test suites. 2b. Weak symbols are supported and the stub implementations of suiteSetUp() and suiteTearDown() are called if there are no user-provided functions. 2c. Weak symbols are supported but overridden by user-provided suiteSetUp() and suiteTearDown() functions.
-
- 11 9月, 2017 1 次提交
-
-
由 John Lindgren 提交于
-
- 10 9月, 2017 1 次提交
-
-
由 balaksh 提交于
-
- 26 8月, 2017 2 次提交
-
-
由 John Lindgren 提交于
-
由 John Lindgren 提交于
The existing implementation was not very good: - It printed all very small values as "0.000000..." - It did not distinguish positive and negative zero - In some cases it printed extra garbage digits for single-precision values (e.g. 3.9e+30 was printed as 3.90000013+30) Tests have been updated to check that we now match printf("%.6g") for 1,000,000 randomly chosen values, except for rounding of the 6th digit.
-