- 11 2月, 2018 1 次提交
-
-
由 Jeremy Hannon 提交于
MISRA 2004 rule 19.10: inside macros, surround each parameter usage with parentheses.
-
- 23 11月, 2017 1 次提交
-
-
由 Shreyas Balakrishna 提交于
-
- 01 11月, 2017 1 次提交
-
-
由 John Lindgren 提交于
-
- 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 1 次提交
-
-
由 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 1 次提交
-
-
由 jsalling 提交于
Check for unsigned types, add 'or equal to' support Consolidate to one function to remove repeated code
-
- 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 提交于
-
- 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.
-
- 14 5月, 2017 1 次提交
-
-
由 Dom Postorivo 提交于
-
- 27 3月, 2017 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
- 22 3月, 2017 4 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
- 21 3月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 19 3月, 2017 1 次提交
-
-
由 Max Bruckner 提交于
-
- 02 3月, 2017 1 次提交
-
-
由 Max Bruckner 提交于
This fixes a compiler warning about a lossy conversion from long unsigned int to int when compiling unity with gcc 6.3.1 and the options -std=c89 -Wconversion -fsanitize=undefined
-
- 01 3月, 2017 1 次提交
-
-
由 Max Bruckner 提交于
This fixes compiler warnings that clang produces with the -Wdouble-promotion compiler option. This only happens if double precision floating point numbers are enabled. The implicit double promotion occurs because numbers of type UNITY_FLOAT are passed into UnityPrintFloat, which expects const UNITY_DOUBLE. This commit fixes it by explicitly casting to UNITY_DOUBLE.
-
- 25 1月, 2017 1 次提交
-
-
由 Crt Mori 提交于
There was a mismatch of definition and declaration of UnityPrintFloat and this commit aligns both on const UNITY_DOUBLE, but then inside it actually uses a positive version of the variable only.
-
- 19 1月, 2017 1 次提交
-
-
由 jsalling 提交于
Used clang-format, which produces noise on stuff you don't care about and requires setting it up to match the existing code base. Kept the potentially useful changes, discarded the rest, some manual tweaking required. It did catch lots of pesky indentation mistakes.
-
- 18 1月, 2017 3 次提交
- 16 1月, 2017 1 次提交
-
-
由 jsalling 提交于
-
- 15 1月, 2017 3 次提交
- 07 1月, 2017 1 次提交
-
-
由 jsalling 提交于
Defensive coding
-
- 31 12月, 2016 1 次提交
-
-
由 jsalling 提交于
-
- 30 12月, 2016 1 次提交
-
- 29 12月, 2016 2 次提交
- 25 12月, 2016 1 次提交
-
-
由 jsalling 提交于
-
- 24 12月, 2016 2 次提交
- 29 11月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
Revised internal type naming scheme to better sandbox Unity away from everything else. Sure, short was nice, but not at the expense of naming collisions.
-
- 20 11月, 2016 1 次提交
-
-
由 jsalling 提交于
Takes about 10 minutes to run all floats, so split into 3 tests for parallel running later. This was useful during development for finding hard corner cases and getting the routine to high quality. Off by default. Note that all floats 16.0 and up can be represented uniquely (in this format) and will round-trip back to the exact same float with sscanf(). This property is true for UnityPrintFloat, despite a few rounding error cases, it will produce output identity. Better comments and refactor on round ties to even Add upper threshold value on round to even feature since numerical precision issues start to give approximations when dividing one large double by another. When tested on float values, using 1e22 gave the fewest rounding errors. Fix warnings from gcc. Some float constants do not behave well in existing tests. Add casts where conversions could be imprecise.
-