redirect UNITY_POINTER_WIDTH to define at last catchable moment. Update older gcc targets to be fully explicit.

Fixed posix default foregroud color to use 39/default instead of 37/light-gray, since was very hard to see on some dark background terminals.
Added Gemfile.lock for rubygems bundle environment consistency.

- rename the custom FLOAT_TRAIT type because the old name was poor

added macros for IS_DETERMINATE and IS_NOT_DETERMINATE

- rework to not bother with any of the ever-changing test frameworks in Ruby (sigh) for self-testing
- started working on cleaner floating point support. more coming.

* Add UNITY_BEGIN and UNITY_END macros to simplify usage
* Improve RUN_TEST to make line_num optional where possible

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

fix parameter type for runAllTests to match header (Thanks toybuilder!)

At least in Microchip XC8 compiler, void (*runAllTests)(void) is treated as a different type from void (*runAllTests)().

Fix the definition of UnityMain to match the declaration by making the runAllTests's (void) parameter list explicit.

fixed format tags for u/int assertions

Fixed initialization of data structure 

Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)

fixed casts in UNITY_TEST_ASSERT_EQUAL_UINT*.  (Thanks Anthony)

fixed double calls to actually use double handler instead of float handler

Support different encoding styles and force to something we can work with

fixed casts in UNITY_TEST_ASSERT_EQUAL_UINT*.  Was previously casting to signed variables and then sign extending the value before casting to final uint and was causing errorneous test failures when executed on arm target

Added more examples

Unknown CLI params get ignored

Print an EOL before printing the TestResult while executing the spec (Thanks Jakob!)

By printing this newline, the filepath of the failing assertion does not get
preceded by the dot which represents a running test.

This gives the advantage, that the complete output of unity can be used as it is
with a makefile in vim. Every error gets displayed in the quickfix and you can
jump appropiately.

Initial import of report parser.

This parser will scan an output file, pull all Unity related tests and summarize them in a report to console or put them in an XML file for use with Jenkins

Conflicts:
	examples/example_3/makefile

build on cygwin