This helps clarity and is more obvious, it looks like a print function

Delete the { ;} braces and semicolon from UNITY_PRINT_EOL to give it expected
  behavior: 1) requires a semicolon 2) works in one-liner if-else statements
If you need "\r\n" for EOL, define as the following to get the same behavior:
  do{UNITY_OUTPUT_CHAR('\r'); UNITY_OUTPUT_CHAR('\n');}while(0)

Unity fixture needs access to this macro to be consistent.
Add #ifndef wrapper for easier redefinition on systems that use "\r\n".

We're going to use the C99 isinf() and isnan() macros wherever possible now. If your compiler doesn't support this, define UNITY_EXCLUDE_MATH_H and it will go back to the old method

Fix some C++ compatibility issues

docs: fix some typos

The intent of UNITY_WEAK_PRAGMA is that we have weak symbols for setUp
and tearDown in unity.o, so that developers can override these symbols
if needed but the link works right if they are not defined.

In order to do this using #pragma, the pragma and the definition of the
function (not the declaration) need to be present in the same translation
unit (source code file).

Previously, the UNITY_WEAK_PRAGMA code was just declaring the setUp
function, but not defining it, which means that developers had to add an
empty setUp function to their tests in order to link.

MISRA rule 19.10: parentheses around macro params

Added parentheses around all macro parameters to resolve MISRA 2004
rule 19.10, "in the definition of a function-like macro, each instance
of a parameter shall be enclosed in parenthesis" as tested with the
IAR EW for 8051 compiler, version 9.20.2.

The only questionable change is in "unity_fixture.h" where the nested
macro DECLARE_TEST_CASE in RUN_TEST_CASE prevents surrounding params
"group" and "name" with parentheses.
However, it appears that macro DECLARE_TEST_CASE isn't used elsewhere,
so I eliminated DECLARE_TEST_CASE and put its expansion directly in
RUN_TEST_CASE.  Now the following header files pass rule 19.10:
* unity.h
* unity_internals.h
* unity_fixture.h

For my own project, this change to the Unity test framework allows me
to include my unit test code to be tested against MISRA rules as well,
instead of just production code, to help enforce style and team
guidelines.

unity_fixture: Make unity_free() NULL-safe

At the start of unity_free(), check mem for NULL, and return immediately
if it is, so we don't crash in this case. This mimics the behaviour of
most free() implementations. Closes #135.
Signed-off-by: NGergely Nagy <algernon@madhouse-project.org>

Fix custom message for 64bit WITHIN_MESSAGE macros (thanks Martyn)

Output used headers from test runner generator

Fixes compiler warning about comparison of signed/unsigned

"usage" output to show .py ext instead of .rb

since this is a python port of "unity_test_summary.rb" the console usage output should say "unity_test_summary.py" instead

the test runner generator now has the ability to also output a header file for the tests, which can get pulled into the test itself if desired.

protect against capturing both declaration and definitions and therefore creating a runner which runs that test twice.

INTPTR_MAX is defined as nothing on some targets (looking at you HP-UX) and therefore these lines would crash. Adding 0 to the check makes these lines always run.

Added back TEST_ASSERT_EQUAL_STRING_MESSAGE() which was (accidentally?) removed some time ago.

Use UNITY_PTR_ATTRIBUTE() in one place where it was (accidentally?) not used.

This eliminates a compiler warning for certain compilers.

Added ability to get number of ignored tests and total number of tests.

Bug fix - ignored tests were incorrectly counted when not selected for running. (Thanks!)

Ignored tests are now correctly skipped if not selected by test name or
by group name.

Fixes #118: unity_output_Spy should use the platform-agnostic macros for memory.

Fixes issues #3 and #116 (Thanks!)

Fixes #116: Allow overrides of the Unity Fixture's memory functions. This enables custom heap implementations to be used with the Unity Fixture.

Fixes #3: unity_fixture tests don't build. unity.c and unity_fixture_malloc_overrides.h neglected to include <stddef.h> even though the reference 'size_t' and 'NULL'.