Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 4 Jun 2002 14:49:29 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ExitProcess() with negative argument -> zero exit status from wait*() Message-ID: <20020604184929.GC16590@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1023172031 DOT 9514 DOT ezmlm AT cygwin DOT com> <20020604172523 DOT 29786 DOT qmail AT wildcard DOT curl DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020604172523.29786.qmail@wildcard.curl.com> User-Agent: Mutt/1.3.23.1i On Tue, Jun 04, 2002 at 01:25:23PM -0400, Bob Byrnes wrote: >I don't want to mix APIs. I just want a clean interface between processes. >Shouldn't cygwin at least try to interoperate with native win32 apps? >Failing to do so really limits its usefulness, IMO. Cygwin uses the values in ExitProcess to signal parent processes in a unix-like way. If that is not the way that you want to use it, then I don't have any other suggestions. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/