This resolves #219. When generating a new module, if all the files to
generate already exist then it fails as before. If some of the files
already exist, then the files that need to be created are created. Any
existing files are not changed.

Also added a bunch of tests for this feature via rspec. Run them from
the test folder with `rake spec`.

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.

Fixed error when path provided in module name.

- configurable case.
- better passing of includes and boilerplate information
- test only pattern
- optional naming conventions for case

removed duplicated declaration of putcharSpy

We can’t guarantee that the built-in function insane will return 1. It might return any other non-negative value. Therefore we need to force it to be 1 so we can use the comparison operator later.

Added ability to inject defines, much like what was built into Ceedling before Ceedling switched to just using this generator.

refactor generate_module so that it can be called as a class from within Ceedling (much like the test runner generator)

Remove extra newline in verbose output format of Fixture

Add option to set NaN not equal NaN for floating point assertions

Fix bug, makefiles for example do not clean on windows

check 'i' limit before using it as an array index.

fix cppcheck "Array index 'i' is used before limits check."

Fix fixture using from C++ sources

Mangling issues, as always.

Finished fixing floating point comparisons. We have streamlined how floats and doubles are checked, but we still can't compare them for equality directly. So we're directly testing for infinite and NaN before checking diffs. Also, we've officially decided that for testing purposes NaN shall equal NaN, +Inf shall equal +Inf, and -Inf shall equal -Inf. It's what most people expect during a test.

Fix warnings if you use UNITY_EXCLUDE_FLOAT

Bugfix Inf equals Inf

Test generator: scrub strings after comments

This fixes #220.

Removing strings from test files is still dangerous, but much
less likely to cause problems after this change to do the
removal after removing comments.

The bug could still manifest if a test file contains defines two
macros, one that contains a single quotation mark and then another
defined somewhere after it that contains a single quotation mark.
Everything in between the aforementioned quotation marks would
still be ignored after this commit, but that is an unlikely
scenario.

Add OSX to travis-ci build.

Print escapes for C strings

Merge build branch.