Bruno Haible wrote: > Paolo Bonzini wrote: >> I agree, but it seems like pipe WaitForSingleObject is broken. You'd >> need a thread polling with PeekNamedPipe, or a busy-waiting loop in the >> main thread altogether. > > Maybe we need to reset the pipe from "signaled" to "non-signaled" state > after [Msg]WaitFor..Objects returns, using ResetState()?
What is ResetState? > Or otherwise, a nearly busy-waiting loop like this: Yes; I'll adapt the poll() emulation to do the same, but I need help testing. Paolo
