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: <3CC51A1F.7040908@goingware.com>
Date: Tue, 23 Apr 2002 03:23:59 -0500
From: "Michael D. Crawford" <crawford AT goingware DOT com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020214
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: c++ char exceptions
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

 > You threw const char*

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.

The only thing that should happen to an exception object after you're done with 
it is that objects thrown by value are destroyed.  In this case the pointer 
would be destroyed, but the memory it points to should not be deleted or anything.

Usually throwing a pointer is not what you really want to do, but it shouldn't 
cause a crash.

Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford AT goingware DOT 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/