Hello,
Gregory Marton <[EMAIL PROTECTED]> writes:
I would surmise that this is an extremely longstanding issue that was
introduced some time before 1.8.1, and that I only noticed it now
because I was trying to use the default build.
As I suggested earlier [0], I think it's just a matter of
non-determinism: there's no guarantee as to when system asyncs are run.
And as I suggested earlier, I think it is very valuable to have guarantees
about when alarms in particular are handled -- that being what they're for.
Grem
--
------ __@ Gregory A. Marton http://csail.mit.edu/~gremio/
--- _`\<,_ .
-- (*)/ (*) No solicitors over 18.
~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~++~~~~~~~
