Changes between Initial Version and Version 1 of Ticket #16995, comment 11


Ignore:
Timestamp:
2018-11-17T07:36:56+01:00 (7 years ago)
Author:
cmuelle8

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16995, comment 11

    initial v1  
    11Oh, for starters we could ramp up {{{AbstractPrimitive.timestamp}}} from {{{int}}} to {{{uint}}}, I guess.  Since it's the same width it won't break serialization objects and should work nicely with whatever is reported by the api servers now.  That'd give room until 2106.  But it's really another issue and does not belong into this ticket..
    22
    3 Greetings
     3EDIT:  [https://docs.oracle.com/javase/tutorial/java/nutsandbolts/datatypes.html Oracle says] that from Java 8 {{{int}}} can be used like {{{uint}}}, but you have to be careful to use static methods like Integer.compareUnsigned(), Integer.divideUnsigned() to treat the variable with.  I have not reviewed the JOSM code enough to tell whether these are already used / are usable to achieve "2038-safeness".