Make all comparison operators on integers available

The setjmp calls are all in TEST_PROTECT() already

Revised internal type naming scheme to better sandbox Unity away from everything else. Sure, short was nice, but not at the expense of naming collisions.

Remove UNITY_FLOAT_VERBOSE entirely, add option UNITY_EXCLUDE_FLOAT_PRINT
Remove some questionable float casts from doubles
Default to Round Ties to Even behavior, add option to Round Ties Away from Zero

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

 For easier automation and searching for a test suite failure

With a buffer long enough, no truncation should be neccesary to format floats.

Buffer length is user settable by defining UNITY_VERBOSE_NUMBER_MAX_LENGTH,
otherwise a sensible default is used based on desired precision.

See: http://stackoverflow.com/a/7235717

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

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.

Compares two strings until maximum n bytes (i.e. strncmp()).

rearranged project to centralize all self-test stuff under test directory. only pull in includes when required.

- 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

- cleaned up pointer support to handle arrays and to give error when you have an illegal configuration

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@135 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e

- rolled in DOUBLE support from Mark Vismer (thanks!)

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@134 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e

- removed TEST_CASE(...) macro from Unity because it's not compatible with a number of compilers.  User will need to define it themselves to use it. (it's an empty define anyway)

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@117 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e

- NOTE: now you need to define UNITY_SUPPORT_TEST_CASES to use TEST_CASE.  This is to avoid problems with compilers that don't support varargs in macros.

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@116 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e

- updated docs to better discuss generator options.

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@104 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@103 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e