Prev: Ball of String
Next: How to have access to all tcl procs and vars in a given interpreter
From: Alexandre Ferrieux on 12 May 2010 12:32
On May 12, 5:36 pm, Jens Haines <bubblegumtr...(a)arcor.de> wrote:
> Am 12.05.2010 10:11, schrieb Alexandre Ferrieux:
>
>
>
> > One thing I fail to understand here is why you completely drop the
> > usleep()-like call for a busy loop, based on the absence of a proper
> > time-reading function.
> > These things are orthogonal: you might very well have a precise
> > sleeper and a less precise time-reader (who knows).
> > Granted, your sleep will be "blind" and drifting, but still more
> > efficient than a busy loop.
>
> > -Alex
>
> Hi Alex,
>
> I could not find an equivalent of usleep in twapi and I'm not very
> familiar with using Ffidl. The usleep approach seems to be the way to go
> if you want to get a real microsecond delay.
>
> I needed to get the program to work quickly though, so I decided to use
> the quick and dirty method with the busy loop. But thank you very much
> for your help anyway.

Argh - you're perfectly right. I keep forgetting how hopelessly
crippled Win32 is...

-Alex
First  |  Prev  | 
Pages: 1 2 3
Prev: Ball of String
Next: How to have access to all tcl procs and vars in a given interpreter