delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
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: | Thu, 8 Jul 2004 14:00:56 +0200 (W. Europe Daylight Time) |
From: | Daniel Lungu <lungu AT nagra DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: negative error status: gcc vs. cl |
Message-ID: | <Pine.WNT.4.21.0407081347560.247-100000@pc0197.nagra-kudelski.ch> |
X-X-Sender: | lungu AT castor DOT hq DOT k DOT grp |
MIME-Version: | 1.0 |
> Feel like bash tcsh on Cygwin mess up with negative exit status from a cl > compiled .exe :) The answer is "don't do that". Use positive values in the range from :) 0 to 255. See :) http://www.opengroup.org/onlinepubs/009695399/functions/exit.html I wouldn't do that. The problem is other did it before me and I need running their .exes in my GNUmakefile. The following prototype would prevent people getting such exit(-2) great ideas: void exit(unsigned status); Daniel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |