This patch fixes testEqualIntArrays in the unity test suite on 16-bit
architectures.

TEST_ASSERT_EQUAL_INT_ARRAY calls UnityAssertEqualIntArray with 'style'
set to UNITY_DISPLAY_STYLE_INT.

UNITY_DISPLAY_STYLE_INT is defined as UNITY_DISPLAY_STYLE_AUTO +
UNITY_DISPLAY_STYLE_INT{16,32,64} (depending on the int width).

However, the switch statement in UnityAssertEqualIntArray has special
cases for the width-specific display styles, but these comparisons
are carried out without clearing the UNITY_DISPLAY_STYLE_AUTO flag.
This means that if 'style' is UNITY_DISPLAY_STYLE_INT, and the int
width is, say, 16, bits, the default case will be hit, and elements
compared as if they were 32 bits wide. Unsurprisingly this causes
a failure in the test named above.

fix bug in target execsion in example makefile

Fix missing #define when UNITY_EXCLUDE_FLOAT is used

Fixing wrong index on string array inequality.  

Added gcc 64-bit for rake

The `build` directory is not created when running make, which yields an error. 

The `build` directory is not created when running make, which yields an error. 

fixed makefile to testunity.out in root directory

C89 patch for MS Visual Studio 2008 Express Edition

     Likewise, place all function prototypes before statements.
     These changes support Microsoft Visual Studio 2008 Express Edition,
       which follows C89-style rules.

Fix: Corrected type of size in GuardBytes to be size_t, not int.

Updates to make Fixture more useful (thanks malsyned! It's nice that someone is helping out with the Fixtures extension!)

Thanks, Bryan.  It's nice to have better documentation (Int config options, in this case)

More details here: http://forums.pragprog.com/forums/123/topics/10126

More details here: http://forums.pragprog.com/forums/123/topics/10126

More details here: http://forums.pragprog.com/forums/123/topics/10901

I love it when things are made clean! Bryan A Jones smooths out some wrinkles in WIDTH detection.

     Document failing approach (sizeof).

Update tests on +/- infinity to work with MSVC++ 2008

     - Change type of floating-point constants to single/double precision
       as appropriate.

Nice work, Bryan... thanks for the cleanup!

     For doubles, make sure all constants are double-precision.

Improved support for special floating point values

testunity.out is being created in the
root directory and was being called from
the 'all' target incorrectly. This is
now fixed.