This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: pid problem found
- To: jmm@raleigh.ibm.com, Cygnus32 <gnu-win32@cygnus.com>, cgf@cygnus.com
- Subject: Re: pid problem found
- From: John Mullee <john@exmachina.net>
- Date: Mon, 08 Feb 1999 15:45:40 +0100
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Organization: Ex Machine Interactive Architects
- References: <199902081430.JAA25094@jmm.raleigh.ibm.com>
- Sender: root@exmachina.net
> (most likely moving to the Win32 event stuff, I'd guess, though all the
> examples that I've seen do explicit checks for incoming messages in the
> code and not something as simple as installing a handler to print one
> integer and exit.
have a look at the WaitForSingleObject and WaitForMultipleObjects api
calls.
The can accept, among other handles, event handles:
CreateEvent OpenEvent SetEvent PulseEvent ResetEvent CloseHandle
as well as process, thread, semephore, mutex, conio and various
file-change
system message handles.
If you'd _really_ prefer to have wrappers that isolate you from all the
OS
dependant low-level bits, think about visiting ACE at:
http://www.cs.wustl.edu/~schmidt/ or news://comp.soft-sys.ace
BTW wow, the new maillist software! realtime!
john
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com