Possibly incorrect explanation of how WaitForSomething works (and how to fix it) [RC and CGF please comment]

[Christopher Faylor]

On Tue, Apr 10, 2001 at 10:36:48PM -0400, Harold Hunt wrote:
>Chris,
>
>> Ouch.  I wasn't aware of this.  Does this project actually belong in
>> the win32-x11 domain, then?  Are you using CreateFile instead
>> of fopen,
>> ReadFile instead of read(), etc?  If so, that means that all of the
>> cygwin mount table and other directory handling will be bypassed.
>
>Oh... uh... well... I haven't had to open a file yet, per se.  Rather, I'm
>been calling functions like PeekMessage, DispatchMessage,
>IDirectDrawSurface_Blt, CreateDIBSection, etc.
>
>I don't really know that those have Cygwin counterparts :)
>
>All the lower level OS layer functions are passed through Cygwin; such as
>opening files, select, sockets, etc.  I haven't touched that code yet.

It's the "yet" that bothers me.  I don't understand your determination to
remove cygwin code in a mailing list called cygwin-xfree.

cgf