DateTimeZone shouldn't have reader/writer parts in the abstract API.

[GoogleCodeExporter]

Third parties should be able to implement their own time zone providers and 
time zones. Currently the read/write part prohibits this, as it uses internal 
types.

Given that the read/write format of time zones is really 
implementation-specific, it shouldn't be part of the abstract API. The current 
format is only used for TZDB, which should be made explicit.

Original issue reported on code.google.com by jonathan.skeet on 23 Jun 2012 at 7:00

[GoogleCodeExporter]

Fixed in changeset 43fe2086cdb9.

Note that there's still at least one internal virtual method, but that's just 
an optimization (which itself uses an internal type) - hopefully this won't be 
a problem.

Original comment by jonathan.skeet on 23 Jun 2012 at 7:54

[GoogleCodeExporter]

I'd still like to separate the IO further, but it's not in the abstract API any 
more.

Original comment by jonathan.skeet on 25 Jun 2012 at 7:09

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by malcolm.rowe on 30 Jul 2012 at 7:26

• Added labels: Milestone-1.0
• Removed labels: V1-Blocker

[GoogleCodeExporter]

Original comment by malcolm.rowe on 10 Nov 2012 at 10:20

• Added labels: Milestone-1.0.0
• Removed labels: Milestone-1.0