The timeZone must be set on the unparsingFormatter as well as the calendar.
compare strings with correct equal method
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.
Declare these test methods.
Need a cast here, since NSString types C strings as const char *, and ours is const unichar *.
Added a property by which you can request a time zone separator. Proposed by @danielctull, although this is a different implementation that lets you specify any character.
Added a failing test case for parsing a date with a(n unusual) time zone separator.
Fix parsing dates with custom time-zone separators.
Return nil immediately if somebody tries to parse nil. (Otherwise, Bad Things will happen when we try to parse the C string.)

Reported by @cruffenach: https://github.com/boredzo/iso-8601-date-formatter/pull/7
Added a test case for issue #15.
Add a test case for #6, adapting the test code from that ticket. Zac's fix works; fixes #6.