This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: c++ char exceptions
- From: "Lassi A. Tuura" <lassi dot tuura at cern dot ch>
- To: "Michael D. Crawford" <crawford at goingware dot com>
- Cc: cygwin at cygwin dot com
- Date: Tue, 23 Apr 2002 13:33:13 +0200
- Subject: Re: c++ char exceptions
- Organization: Northeastern University, Boston, USA
- References: <3CC51A1F.7040908@goingware.com>
> 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/