Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 41053 invoked from network); 20 Apr 2004 03:12:57 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Apr 2004 03:12:57 -0000 Received: (qmail 42588 invoked by uid 500); 20 Apr 2004 03:12:36 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 42567 invoked by uid 500); 20 Apr 2004 03:12:36 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 42550 invoked from network); 20 Apr 2004 03:12:36 -0000 Date: Mon, 19 Apr 2004 23:12:43 -0400 (EDT) From: Cliff Woolley X-X-Sender: jcw5q@cobra.cs.Virginia.EDU To: "Mathihalli, Madhusudan" cc: dev@apr.apache.org Subject: Re: [PATCH] New api's apr_block_signal and apr_unblock_signal In-Reply-To: <16A24B6050584143978000646801E93501275ED4@cacexc03.americas.cpqcorp.net> Message-ID: References: <16A24B6050584143978000646801E93501275ED4@cacexc03.americas.cpqcorp.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Mon, 19 Apr 2004, Mathihalli, Madhusudan wrote: > Since a lot of the async signals are blocked by default, I thought > it'll be good to provide a apr_(un)block_signal() api for those who want > to block/unblock only select signals. Here's a patch to do that. Is this portable? (Admitting my ignorance of the Win32 API here.) PS: the names should be apr_signal_block and apr_signal_unblock instead. --Cliff