Implications of adding an offset to Timestamp
Locked
Implications of adding an offset to Timestamp
 
|
AR 27763 in VisualWorks 7.10's build today (aug12.3) adds an offset from UTC to Timestamp.
Now math can be done on Timestamps without requiring the application program to maintain proprietary meta-knowledge of the time zones of each component of the equation, for example.
Now ISO-8601 timestamps will properly print, including the offset.
I have included a short pdf file with this message which describes the effects and shows how the different ways to instantiate a Timestamp affect what offset it contains.
Reading an ISO-8601 compliant text representation, for example, contains offset information and so results in a Timestamp with its offset matching the time zone indicated in the text string processed.
Other paths to creating Timestamps will result in other offsets, as described in the document.
Some methods are deprecated as a result of this addition, but will not be removed for some time, most likely not before a major version revision of VisualWorks, which would be 8.0 at this writing. Some may be maintained as convenience methods based upon feedback from users.
Additional methods for reading ISO-8601 text representations which are not exactly conformant to VisualWorks' implementation will be added in subsequent builds of 7.10, and will be described as to when and why you would want to use them. This will be in an upcoming build, so please keep in mind that there is more to come in that regard.
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Timestamp_Offsets.pdf (141K) | Free forum by Nabble | Edit this page |