Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
GoogleCodeExporter opened this issue Mar 15, 2015 · 4 comments
Closed

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

GoogleCodeExporter opened this issue Mar 15, 2015 · 4 comments
Labels
bug
Milestone
1.0.0

Comments

@GoogleCodeExporter
Copy link 

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
2 participants
@malcolmr @GoogleCodeExporter