`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.

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!)

Formatting source code to existing style

Removing unnecessary function prototypes, inline PrintOk/Fail

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.

Altered the rake build so that it passes. The example_3 shows off
some failing tests, so the rake build has to ignore those.
Update .gitignore file with executables from examples

Delete clang flags that were disabled with -Wno-*

No print masking of integers, bounds on hex printing (Thanks!)

Optional UNITY_EXCLUDE_SETJMP_H, different control flow

This reverts commit ee382194.
Removing these changes per coding standard, after the code review

Quell warnings about pointer to integer cast

Fix bug in DOUBLES_EQUAL in unity_fixture.h

With a wider integer width than a pointer, gcc can still warn
when you cast a pointer. Strange but true. To see these warnings
compile with gcc -m32, 32-bit target, and enable UNITY_SUPPORT_64

Using this option changes the control flow of Unity, but is useful on
constrained embedded systems. You can't fully simulate the power of
'longjmp' with just 'return', but Unity still works well, all tests pass.

Move longjump inside caller, to functions returning 'void'
This single function needed to change to allow optional setjmp.h

The setjmp calls are all in TEST_PROTECT() already

Fixture - Remove duplicate output of test name in verbose mode

Organize Makefile so clang works on all platforms, warnings are set

Remove promotion warnings on float constants, Inline the isneg/ispos macros

Always run the tearDown() even if test is ignored

Cleanup floating point print testing, update docs

Rename UNITY_SKIP_EXECUTION to RETURN_IF_FAIL_OR_IGNORE

Thanks for the walkthrough (and all the original work!). Your logic seems solid to me. :)

Defensive coding