Eric
"Eric Winger" <
[hidden email]> wrote in message
news:
[hidden email]...
> In trying to coerce a st TimeStamp object to an external FILETIME, I
> found the following anomoly...
Thanks for the bug report. On cursory examination I think the problem here
is that the method LocalFILETIME>>asUTC is implemented as:
^self class fromLocalTime: self
But should be implemented as:
^FILETIME fromLocalTime: self
I think this was broken when an attempt was made to remove a circular ref.
between the FILETIME and LocalFILETIME classes, which meant that those two
classes could never be stripped from a deployed image, probably in the D4
release.
(Note that in D4 that FILETIMEs always print/display in local time, even if
stored in UTC).
Regards
Blair