> Without proper kernel-level support for poll, we probably can't have a
> poll on Windows that suspend the thread until an event happens; we'll
> have to accept a bit of polling. But I believe that looking and
> quacking like POSIX is better than doing something the standard says
> shouldn't happen. Wasting CPU cycles is IMO better than returning 0 in
> this case (but perhaps I'm biased as I've been burned by this
> behavior). Yielding the thread and/or sleeping a bit on retry might be
> a better compromise, though.
Ping? Should I re-post the patch with SwitchToThread() squashed in?