Article View: borland.public.cppbuilder.nativeapi
Article #10267Re: Problem with WaitCommEvent in thread
From: Benjamin Pratt
Date: Tue, 11 May 2004 19:01
Date: Tue, 11 May 2004 19:01
9 lines
1291 bytes
1291 bytes
Martin, The handle cannot be used 'simultaneously' by two threads. The second will block until the first finishes. In the case of WaitCommEvent, this may be a long time. If you do not want to use overlapped I/O, you can open two seperate handles to the port, one for each thread. Have a look at this thread which recently covered this very issue: http://tinyurl.com/yspwn
Technical Details
Message-ID:
<40a1213b@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!controlnews3.google.com!news2.google.com!news.maxwell.syr.edu!c03.atl99!news.usenetserver.com!newsfeed.media.kyoto-u.ac.jp!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<40a092fd$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10cc67,4298e6c7d8d30497 X-Google-Attributes: gid10cc67,public From: "Benjamin Pratt" <benjamin.pratt.getridofthis@verizon.net> Newsgroups: borland.public.cppbuilder.nativeapi References: <40a092fd$1@newsgroups.borland.com> Subject: Re: Problem with WaitCommEvent in thread Date: Tue, 11 May 2004 12:01:40 -0700 Lines: 11 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 NNTP-Posting-Host: 68.26.59.205 Message-ID: <40a1213b@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1084301627 68.26.59.205 (11 May 2004 11:53:47 -0700) Path: arc1-ca.pugleaf.net!controlnews3.google.com!news2.google.com!news.maxwell.syr.edu!c03.atl99!news.usenetserver.com!newsfeed.media.kyoto-u.ac.jp!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail