Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <3CC54679.FE036A82@cern.ch>
Date: Tue, 23 Apr 2002 13:33:13 +0200
From: "Lassi A. Tuura" <lassi DOT tuura AT cern DOT ch>
Organization: Northeastern University, Boston, USA
X-Accept-Language: en
MIME-Version: 1.0
To: "Michael D. Crawford" <crawford AT goingware DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: c++ char exceptions
References: <3CC51A1F DOT 7040908 AT goingware DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> That shouldn't matter.  At the worst it should mean that the exception is not
> caught by any of the catch clauses given, so the "return 0" would be taken.

It does matter -- in this case the exception was not handled, and
therefore terminate() gets called, which probably called abort().  That
is, the "return 0" is never taken, the exception leaks outside main().

//lat
-- 
Behold the turtle.  He makes progress only when
he sticks his neck out.  --James Bryant Conant

--
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/