<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
David T. Lewis wrote:
<blockquote cite="mid:20140526190030.GA20493@shell.msen.com" type="cite">
<pre wrap="">On Mon, May 26, 2014 at 06:16:03PM +0000, J. Vuletich (mail lists) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Quoting "David T. Lewis" <a class="moz-txt-link-rfc2396E" href="mailto:lewis@mail.msen.com"><lewis@mail.msen.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">...
</pre>
<pre wrap="">Ian did a build of the Windows VM that should have the necessary support.
Try
the Squeak4.1.2.2612 VM from <a class="moz-txt-link-freetext" href="http://squeakvm.org/win32/">http://squeakvm.org/win32/</a>.
</pre>
</blockquote>
<pre wrap="">That VM fails for
<primitive: 'primitiveUtcWithOffset'>
<primitive: 240> primUtcMicrosecondClock
<primitive: 241> primLocalMicrosecondClock
</pre>
<blockquote type="cite">
<pre wrap="">One thing to note - if the primitive is not present, DateAndTime will fall
back on the old logic, and it should produce reasonable results.
</pre>
</blockquote>
<pre wrap="">Yes, Cuis already does that... I'd prefer to be able to assume that
any future VM will provide <primitive: 'primitiveUtcWithOffset'> and
clean the code. Would that asking for too much?
</pre>
</blockquote>
<pre wrap=""><!---->
You should expect the following two primitives to be present in all VMs
(comments are from the VMM trunk implementations):
primitiveUtcWithOffset
"Answer an array with UTC microseconds since the Posix epoch and
the current seconds offset from GMT in the local time zone. An empty
two element array may be supplied as a parameter.
This is a named (not numbered) primitive in the null module (ie the VM)"
primitiveUTCMicrosecondClock
"Answer the UTC microseconds since the Smalltalk epoch. The value is
derived from the Posix epoch (see primitiveUTCMicrosecondClock) with a
constant offset corresponding to elapsed microseconds between the two
epochs according to RFC 868."
</pre>
</blockquote>
Since both answer microseconds, then second seems a little confusing.
Calling them something like #primitivePosixUtcWithOffset and
#primitiveSmalltalkUtc seems more intention revealing.<br>
<br>
cheers -ben<br>
</body>
</html>