From: leisner AT sdsp DOT mc DOT xerox DOT com ("Marty Leisner")
Subject: Re: SIGALRM doesn't work?
27 May 1997 21:46:59 -0700
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <9705271739.AA14892.cygnus.gnu-win32@gnu.sdsp.mc.xerox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: exmh version 2.0gamma 1/27/96
Original-To: Sergey Okhapkin <sos AT prospect DOT com DOT ru>
Original-Cc: "'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>,
        "'Jimen Ching'" <jimen AT adtech-inc DOT com>
In-Reply-To: Your message of "Fri, 16 May 1997 01:12:17 PDT."
             <01BC61F5 DOT 4E5DE770 AT gater DOT krystalbank DOT msk DOT ru> 
Original-Sender: owner-gnu-win32 AT cygnus DOT com

> Jimen Ching wrote:
> > Hi, could someone verify that the following program does not cause an 
> alarm signal to be generated?  Does SIGALRM work at all with b18?  That's 
> the version I have on my NT
> 
> SIGALRM and other timer stuff are not supported in b18.
> 

And its not supported in djgpp.

Its incredibly useful.  Is there a way to generate a signal
in a win32 program using the native api?



-- 
marty
leisner AT sdsp DOT mc DOT xerox DOT com  
The Feynman problem solving Algorithm
        1) Write down the problem
        2) Think real hard
        3) Write down the answer
                Murray Gel-mann in the NY Times




-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".