Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: c++ char exceptions From: "Michael D. Crawford" To: "Lassi A. Tuura" Cc: cygwin@cygwin.com In-Reply-To: <3CC54679.FE036A82@cern.ch> References: <3CC51A1F.7040908@goingware.com> <3CC54679.FE036A82@cern.ch> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: 25 Apr 2002 00:33:02 -0500 Message-Id: <1019712784.423.254.camel@pishi> Mime-Version: 1.0 You're right, I wasn't thinking, if an exception isn't caught before it leaves main it aborts the program. So maybe codewarrior has a bug! Mike On Tue, 2002-04-23 at 06:33, Lassi A. Tuura wrote: > > 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/ > -- Michael D. Crawford GoingWare Inc. - Expert Software Development and Consulting crawford@goingware.com http://www.goingware.com/ Tilting at Windmills for a Better Tomorrow. -- 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/