On Feb 18, 2013, at 3:58 AM, J Altfas wrote:
> Certainly agree that leaving out usleep was an oversight, considering how
> simple it is to include it. While I'm pretty sure many of the posix functions
> are not optimum in an srfi-18 threaded environment, file-select, sleep, and
> friends are st
On Mon, 18 Feb 2013 14:36:33 -0600 Jim Ursetto wrote:
> On Feb 18, 2013, at 3:58 AM, J Altfas wrote:
>
> > Certainly agree that leaving out usleep was an oversight, considering how
> > simple it is to include it. While I'm pretty sure many of the posix
> > functions are not optimum in an srfi-1
On Sun, Feb 17, 2013 at 9:07 AM, Mario Domenech Goulart
wrote:
> Hi Andrei,
>
> Amazing! Thank you. I've added them to the coop. They'll be available
> for chicken-install in some minutes.
>
> Please, keep one eye on the salmonella report tomorrow. It'll be
> available at http://tests.call-cc.
Felix scripsit:
> I think usleep(3) is not available on Windows. There is probably a win32
> equivalent, though.
The Woe32 version is Sleep(), which accepts an argument in milliseconds,
and puts the current Windows thread to sleep. However, the default
resolution is 10-15 ms. If you want to cha
>
> I don't know why sleep(3) was implemented in the posix unit and usleep(3) was
> not. thread-sleep! is preferable to either, though, in my opinion.
I think usleep(3) is not available on Windows. There is probably a win32
equivalent, though.
cheers,
felix
__
On Sun, 17 Feb 2013 21:16:56 -0600 Jim Ursetto wrote
> On Feb 17, 2013, at 4:18 PM, J Altfas wrote:
>
> > Hello,
> >
> > Using 'file-select' as a sub-second sleep procedure works without hitch
> > under csi:
> >
> > (define (sleeper tm)
> > (let ((currms (current-milliseconds)))
> > (let-values
Florian Zumbiehl writes:
> But usually, good APIs would declare buffer sizes as size_t, which there
> doesn't seem to be any corresponding foreign type specifier for!?
Actually, a foreign type specifier for size_t was added in 4.7.0 (called
size_t, too). Apparently it wasn't added to the document
