Fix docs.

Starting to enforce our coding style. The first step is that we’ve pulled in Rubocop to check out Ruby syntax. There is likely a bit of customization to do yet AND there is definitely that backlog of todo’s that we just told it to ignore.

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

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

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

- fixed a few bugs in fixtures to get it to pass against our standard compilers
- added extern of OUTPUT_CHAR method to keep compilers from complaining

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

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@106 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@99 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e

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

- improved error reporting for generate_test_runner

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

- added ability to do suite_setup and suite_teardown to runner

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

- organized targets into a subdirectory
- cleaned up testing so floats and 64-bit ints are only tested if enabled


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

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

- restored makefiles to working condition
- updated files to include copyright notice
- fixed bug in string array comparisons
- ignored tests no longer run teardown
- tests failing for uncaught cexceptions now get exception id reported

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

- updated unity helper examples to get them working again
- got examples running again

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

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

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

- added color coding to output

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

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

Converted MSP430 config to YAML format. Still need to update Unity to support 16-bit and big-endian to get to work.
Modified Unity to use test suite generator in preparation for updates for 16-bit and big endian changes

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

Need to figure out what to do about IAR MSP430

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

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

Examples projects, more complete documentation, and other beautification.  It brings a tear to the eye.

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

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