Bug in Win32file WaitCommEvent ???

[Grant Edwards]

In article <arg8nn$kr2$0 at 216.39.172.122>, Bengt Richter wrote:
> On 20 Nov 2002 01:07:57 GMT, Grant Edwards <grante at visi.com> wrote:
> [...]
>>> 
>>> Sounds like the mask location is safe if you don't call
>>> GetOverlappedResult??
>
> OTOH it looks to me pretty sure that a persistent LPOVERLAPPED
> structure at least is expected for the duration of the
> background operation.
> 
> and, thinking about it, it says,
> 
> "GetOverlappedResult reports the success or failure of the
> operation, and the variable pointed to by the lpEvtMask
> parameter is set to indicate the event that occurred."
> 
> but you don't re-specify lpEvtMask with that call, so I think I
> would agree with your original take on all this.

Assuming the text on the MSDN page is correct.

> They wouldn't just force a wait all the time, would they?

I've seen plenty of apps that assume it doesn't wait all the
time.  If I had a C compiler and knew how to write a simple
console app for Win32, it would be easy enough to figure out
how it really does work.  The Win32 guys I work with directly
all write device drivers and none of them know how the
user-land API works.

> Though I can imagine that being a tempting temporary quick fix
> for something, and temporariness sometimes stretches.

-- 
Grant Edwards                   grante             Yow!  Here I am in the
                                  at               POSTERIOR OLFACTORY LOBULE
                               visi.com            but I don't see CARL SAGAN
                                                   anywhere!!