The timeZone must be set on the unparsingFormatter as well as the calendar.
Fix compile error for parser test
Use the offset against GMT for the provided date, not current date

A date in the past may have been under a different absolute offset than we currently are in.
compare strings with correct equal method
Starting work on a proper unit test suite.
Implemented the test of parsing GMT dates.
Include stdbool and tgmath in the test project's prefix header.
Added unparsing tests, two of which fail because of time-zone mishandling.
Test parsing a third variant of this GMT date.
Merge pull request #10 from zacwest/fix-daylight-savings-time

Fix daylight savings time unparsing (at least for Pacific Time). Refs #6.
Added failing test for millisecond precision support.
Added Xcode implicit workspace, ignore user data.
Support parsing of dates with millisecond accuracy.

NSDateComponents doesn't support fractional seconds, but we can still
add the extracted milliseconds to the parsed date afterwards.
Merge pull request #4 from carllindberg/master

Fixes issue #3: Set the timeZone of the unparsingFormatter. Fixes a test failure.
Corrected the accuracy parameter to STAssertEqualsWithAccuracy.
Clarified that this is a fraction of a second, not a whole number of milliseconds. Also some style consistency fixes.
Merge branch 'support-millisecond-precision' from lukeredpath's fork, with a couple of fixes from me.
Merge @mastohhh's fix for throwing away the unparsing formatter unnecessarily when includeTime is turned on.
Added a test for an unusual time separator character. Fails, at least with Unicode characters (since the implementation is 8-bit).
Switched the parser from unsigned char to unichar, thereby enabling handling of any valid unichar time separator. Fixes the test failure introduced in previous commit.