1. 08 4月, 2019 1 次提交
  2. 12 3月, 2019 1 次提交
  3. 31 1月, 2019 1 次提交
  4. 25 1月, 2019 3 次提交
  5. 29 11月, 2018 2 次提交
  6. 31 10月, 2018 3 次提交
  7. 28 10月, 2018 1 次提交
  8. 27 10月, 2018 1 次提交
  9. 19 10月, 2018 1 次提交
  10. 14 10月, 2018 1 次提交
  11. 12 9月, 2018 1 次提交
  12. 29 7月, 2018 1 次提交
  13. 26 7月, 2018 1 次提交
    • R
      Fix LESS_OR_EQUAL_MESSAGE asserts for HEX32/HEX64 · 6a1d2e8d
      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()
      6a1d2e8d
  14. 18 7月, 2018 1 次提交
    • X
      Flush unity output before a potential longjmp · 2c5d09bf
      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
      2c5d09bf
  15. 18 2月, 2018 1 次提交
  16. 11 2月, 2018 2 次提交
  17. 23 11月, 2017 1 次提交
  18. 08 11月, 2017 4 次提交
  19. 01 11月, 2017 1 次提交
  20. 31 10月, 2017 1 次提交
  21. 24 10月, 2017 1 次提交
  22. 09 10月, 2017 2 次提交
    • J
      Make weak symbol usage more portable: · df78aade
      John Lindgren 提交于
      - Enable support for Green Hills Software compiler
      - Define weak implementations only once except on Windows
      df78aade
    • J
      Fix link errors with MinGW. · a7e8797e
      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.
      a7e8797e
  23. 21 9月, 2017 3 次提交
  24. 14 9月, 2017 1 次提交
    • J
      Allow suiteSetUp() and suiteTearDown() to be provided as normal C functions. · 2593c31b
      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.
      2593c31b
  25. 11 9月, 2017 1 次提交
  26. 10 9月, 2017 1 次提交
  27. 26 8月, 2017 2 次提交
    • J
      Make code C89-compliant. · 2ae2bdb3
      John Lindgren 提交于
      2ae2bdb3
    • J
      Rewrite UnityPrintFloat to match printf("%.6g"). · 0e7eb545
      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.
      0e7eb545