- Added ability to surround filter strings in either type of quotes
- Added ability to filter on multiple test strings as a comma delimited list
- Added ability to filter on test_file:test_name
- Added ability to use alternate syntax for filter of -f="blah"

Updated method of testing generate_test_runner script to be a FUNCTIONAL test instead of a perfect code match. Backfilled most tests and added some coverage not previously present. Still need to test new command line args and a few cmock details.

Script verification hasn't been added yet.

add unity_to_junit.py (Thanks!)

Change comments style to compile with std=c89 (Thanks Andy... and everyone else who helped make this decision)

Add template example unity_config.h file. (Thanks wolf99!)

As recommended in PR #193

The class gives back to the community: better documentation produced for the class and now part of the open source project

add UNITY_OUTPUT_FLUSH to make sure we get the output we need on aborted tests and whatnot.

100% code coverage for Unity project (Thanks jsalling!)

 Add test for failure count and UnityEnd return value
 Cover printing escape codes with length parameter
 Full statement coverage

 More statement coverage on NULL input feature

 Get test coverage on this feature for int, float, & double

 Add config flag for 64-bit, max covered lines even with 32-bit compilers
 Always print uncovered lines, delete separate make target

 Remove what looks like an overflow check. 'divisor' cannot overflow
  since it is the same type as 'number' and cannot be greater.

Add option to print FAILED instead of FAIL during the summary

 For easier automation and searching for a test suite failure

Thanks @rikvdh for catching some instances where we should have been using isnan and such that were missing!

Add Unity Fixture to the travisCI build and restore header declaration of UNITY_OUTPUT_CHAR

Fixup issues when compiling with clang -Wmissing-variable-declarations

 This solves the warnings from -Wredundant-decls when overriding the
  OUTPUT function with a function declared in another header.
 It's better this is the non-default option, since using it requires either
  a declaration of the new function OR a preprocessor guard on declaring
  UNITY_OUTPUT_CHAR (as in unity.c here), in every file using the function.
 See Pull Request #185 for more.

 These were aimed at preventing the internals header from declaring
  a prototype for 'int UNITY_OUTPUT_CHAR(int);'. The second part fixed
  an omitted declaration in the tests caused by the first commit.
 Will replace the default behavior & add an option for this in next commit