Starting to enforce our coding style. The first step is that we’ve pulled in Rubocop to check out Ruby syntax. There is likely a bit of customization to do yet AND there is definitely that backlog of todo’s that we just told it to ignore.

Fix -Wconversion with gcc-4.3

Turn UNITY_OUTPUT_FLUSH off by default. Added a quick-define for the most common case: UNITY_USE_FLUSH_STDOUT. Clarified documentation. Fixes issue #269

Fix gcc warning with ubsan and -Wconversion

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

Fix warnings with -Wdouble-promotion

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.

Fixed incorrect TEST_PROTECT explanation in readme

Enhance parseOutput.rb to support Unity fixture output

Fixed typo for TEST_PROTECT in readme

`setjmp` returns 0 on direct invocation, and non-zero when returned to from `longjmp`. Because `TEST_PROTECT` checks the return value of `setjmp` against 0, checking the return value of `TEST_PROTECT` against 0 is incorrect in the readme.

unity.h and unity_fixture.h output their results in different string formats. This parseOutput.rb script already parsed the unity.h output to generate a JUnit-style XML summary which could be parsed by CI servers to graph the history of test pass/fail results. The changes in this commit allow the script to also handle the output format of unity_fixture.h which utilizes groups to add a layer of organization for tests.

The changes in this commit were authored by Justin Seifi, my coworker, who has approved of me submitting his work back to this open source framework repo.

Test for printing max width of a hex number, back to 100% test coverage

Align definition and declaration of UnityPrintFloat

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.

Correct clean target and print test fails during coverage in Makefile

Compile examples during continuous integration

If, longer term, the Travis-CI support for 32-bit is inconsistent
the lines that failed are:
 - make -s DEBUG=-m32
 - cd ../example_3 && rake
Add target 'ci' for building examples with -Werror

Option to exclude CppUTest compatibility asserts (Thanks!)