There was already some space reserved as a guard, added check for writes
 before the beginning of the buffer. Did not change the 'overrun' message.
 Underrun buffer writes are likely to be a more rare case.

Feature - remove dependencies from Fixture, add internal heap option (Wow! Thanks jsalling!)

 This feature removes the dependency on malloc/free for constrained
  embedded systems without a heap. It uses a static heap inside
  Unity Fixture. Setting UNITY_INTERNAL_HEAP_SIZE_BYTES sizes the heap.
 Add tests for new option, add targets to makefile for running tests.
 UNITY_FIXTURE_MALLOC for Fixture use only, remove from unity_output_Spy.c.

Added support for mocks in sub-directories. (Thanks pmendham! This is helpful!)

feedback from @mvandervoord (Thanks).

 Consistent use of one-liners and NULL

 Help failures in the spy by adding filename and message to output

 For redefinition of UNITY_FIXTURE_MALLOC/...FREE use both or replace both.
 Clean up whitespace, remaining void*, and comment.

This supports mock headers of the form:
    #include "some/dir/MockMyCode.h"
Where the mock name is actually MockMyCode.

I *think* this is the most common scenario when working with mocks
in subdirectories but if not this could be modified to support
alternate schemes.

Removed unecessary output when generating a test runner (Thanks pmendham!)

Fixture rakefile has a conflict defining UNITY_OUTPUT_CHAR

Two small changes to runner generation

Changed the guard syntax as it was cumbersome for header files in deep
sub-directories. Added framework/mock includes to make the header file
stand alone. Made sure that a valid prototype was generated in the case of
no arguments (void).

This allows alternative entry points. This is intended for the
integration of the unit test into a larger system or for it to be used with
a platform/OS which requires an application entry point other than main. At
the moment there is no way to change the type signature.

 Make core Unity rakefile helper follow Fixture define procedure.
 This commit reverts parts of 36e2ca19.

 Delete unused variables and empty functions
 Make setUp & tearDown (used in Unity core) optionally defined
  if 'weak' linking is present

Bugfix for UnityAssertNumbersWithin()

Fixture - require spy or else ignore tests

Fix trailing whitespace CRLF, no code changes

 Make subtraction result unsigned, change prototype & casts in internals.
 If "actual - expected" overflowed, it wrapped to a negative number,
  but would fit in an unsigned type, example is INT_MAX - (-1) = INT_MIN
 For correctness, 'delta' should be unsigned too. Passing in a negative
  number always passed. The delta can be between INT_MAX & UINT_MAX.

 32 or 64 bit test will fail if compiled with -m32 or -m64, repectively
  on clang or gcc
 Fixes to the failures will follow

 Now that the project is using .gitattributes, get rid of CRLF in the repo.

Add tests for printing numbers, interface for spying on output strings (Thanks! I like this idea!)

- tweak docs

Refactor Fixture, no EOL with ignored tests, add a Makefile for Fixture tests 

Fix printing of largest negative number

Include <stdio.h> (for sprintf) when using UNITY_FLOAT_VERBOSE (thanks pacheco017!)

 Add CFLAGS in Fixture Makefile to catch C99 rules with '-pedantic'

 Ignore tests that need the Spy if we are not building with it

 Updated clang and gcc targets. Fixed spelling of LIMITS, which breaks the
  gcc_auto_sizeof.yml build.
 Commented -Wunreachable-code, Unity won't build on OSX clang with it,
  error in unity.c:769 & 932: 'default: break;' case.

 If Unity core is compiled with UNITY_OUTPUT_CHAR = putcharSpy, these tests
  will run, otherwise they are ignored and print a message
 Includes an implementation of putcharSpy, which allows checking the I/O
  from Unity during a test. Follows closely from the Fixture spy
 Tricky macros determine if putcharSpy is injected