On Fri, 2 Mar 2007, Avdi Grimm wrote:

> On 3/1/07, Tomas Pospisek <tpo2 / sourcepole.ch> wrote:
>> However, this applies in exactly the same way to libc-select as well and 
>> thus replacing the select/gettimeofday mechanism by libc-sleep should 
>> at least work no worse. Objections?
>
> My first reaction was:  good god, the scheduler uses wallclock time?!
> Speaking as someone who works on realtime systems (and thus has to
> think about scheduler implementation often), this is never a good
> idea. I don't know the background for Ruby's scheduler design, but
> normally I'd regard a scheduler which uses wallclock time as just
> plain *broken*.  I'm heartily in favor of changing it to something
> which isn't dependent on the clock.

Do you know of any cross-platform aka POSIX call where the returned time 
is strictly increasing? How do other green thread implementations handle 
this problem?
*t

--
-----------------------------------------------------------
   Tomas Pospisek
   http://sourcepole.com -  Linux & Open Source Solutions
-----------------------------------------------------------