>At times, we do (or else I wouldn't have bothered looking into this
>issue at all ;-) The best solution I came up with was to exploit native
>timer services and then reset the interrupt check counter in order to
>force an interrupt check. The speed loss is almost neglectable (I
>measured below 1%) which is a number I am willing to trade for accurate
>timing behavior.
>
>Cheers,
>   - Andreas

Alright do you have a patch lurking somewhere?

I'm assuming you need an external call in primitiveSignalAtMilliseconds

also if we do have hosted OS timer support could we alter
primitiveResponse the timerPending logic to avoid looking at the clocks.


-- 
--
===========================================================================
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
===========================================================================