RFR 8068730: Increase the precision of the implementation of java.time.Clock.systemUTC()

Stephen Colebourne scolebourne at joda.org
Mon Jan 12 11:40:57 UTC 2015

On 12 January 2015 at 11:36, Daniel Fuchs <daniel.fuchs at oracle.com> wrote:
>> In java.time.Instant, a readObject() has been added. However, I don't
>> believe this will ever be called because Instant has a writeReplace()
>> method and so is not deserialized. (There may be some security related
>> "evil serialization stream" reason why readObject() should exist, I
>> can't say).
> I have not touched java.time.Instant in this patch.

Oops, I misread the webrev!

>> I do believe that this change means that a new method should be added
>> to Clock however:
> Ah - I see. I didn't think of that. It looks like a sensible
> RFE. Agreed.

I look forward to that webrev!


More information about the core-libs-dev mailing list