Re: [Chicken-users] current-time on 32-bit hardware

[Felix]

From: Nicolas Pelletier <address@hidden>
Subject: Re: [Chicken-users] current-time on 32-bit hardware
Date: Mon, 15 Nov 2010 10:47:36 +0900

> Hello,
> 
> On Fri, Jul 30, 2010 at 21:13, Felix
> <address@hidden> wrote:
>>
>> If you are adventurous, you can try out the "flonum-milliseconds"
>> branch in the git repository, where I made all the necessary changes
>> (quite a lot, in fact). Feedback would be great, since I don't have
>> decent testing code for multithreading.
> 
> It's been quite a while since this message... I have backported the
> flonum-milliseconds code for my 4.3.0 installation and used it since
> the beginning of August. I also added a patch to runtime.c to use
> times() to compute dates instead of gettimeofday(). The two
> multi-threaded applications I have that use Chicken include each a
> handful of threads, finite state automatons, timers, and mutexes. They
> spawn several other processes, talk to them through sockets and pipes,
> parse their output, filter/modify/group log messages and events
> (maximum 1 event every 2 ms), throw and catch some exceptions and also
> use dynamic-wind and call/cc.
> 
> While 1 event per 2 ms max is not exactly blindingly fast, these
> applications have passed soak tests for a hundred hours each, and are
> deployed at several customers' sites since the beginning of September,
> with nobody complaining so far. So I vote for the inclusion of the
> flonum-milliseconds patch :-)
> 

Very good. It has been included for a while now. Thanks for
testing this.


cheers,
felix