: RFR: JDK-8033662 DateTimeFormatter parsing ignores
withZone()
References: CACzrW9BTWhehV+oC-aEQAEkLtTA4XO6z-F5=jevyv-d35+y...@mail.gmail.com
mailto:CACzrW9BTWhehV+oC-aEQAEkLtTA4XO6z-F5=jevyv-d35+y...@mail.gmail.com
CACzrW9BcmmesdKQBrtgrAc=12hn3uowjvwzxskmfcksajea...@mail.gmail.com
DateTimeFormatter parsing ignores withZone()
References:
CACzrW9BTWhehV+oC-aEQAEkLtTA4XO6z-F5=jevyv-d35+y...@mail.gmail.comCACzrW9BTWhehV+oC-aEQAEkLtTA4XO6z-F5=jevyv-d35+y...@mail.gmail.com
CACzrW9BcmmesdKQBrtgrAc=12hn3uowjvwzxskmfcksajea...@mail.gmail.comCACzrW9BcmmesdKQBrtgrAc=12hn3uowjvwzxskmfcksajea
Hi there,
It would be great if I could get a review please.
The patch is viewable in plain text at JIRA (for IP reasons):
https://bugs.openjdk.java.net/secure/attachment/19216/ParseWithZone.patch
The same patch is viewable in a nice format at GitHub
https://gist.github.com/jodastephen/9505761
Hi Stephen,
Given the fact that the parser context is no longer public, the parsed from the
formatter is either unresolved or resolved, just wonder if we really need those
effective chrono and zone fields in Parsed. It appears perfect for me to
simply
keep these info inside the parser context
ping
On 12 March 2014 12:29, Stephen Colebourne scolebou...@joda.org wrote:
This is a request for review of this bug:
https://bugs.openjdk.java.net/browse/JDK-8033662
and the duplicate:
https://bugs.openjdk.java.net/browse/JDK-8033659
The javadoc of the method
This is a request for review of this bug:
https://bugs.openjdk.java.net/browse/JDK-8033662
and the duplicate:
https://bugs.openjdk.java.net/browse/JDK-8033659
The javadoc of the method java.time.format.DateTimeFormatter::withZone says:
If no zone has been parsed, then this override zone will be
