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
content-class:	urn:content-classes:message
Subject:	RE: c++ char exceptions
MIME-Version:	1.0
Date:	Tue, 23 Apr 2002 18:36:03 +1000
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
Message-ID:	<FC169E059D1A0442A04C40F86D9BA7600C5ED3@itdomain003.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Michael D. Crawford" <crawford AT goingware DOT com>, <cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g3N8dkN09590

> -----Original Message-----
> From: Michael D. Crawford [mailto:crawford AT goingware DOT com] 
> Sent: Tuesday, April 23, 2002 6:24 PM
> 
> Usually throwing a pointer is not what you really want to do, 
> but it shouldn't 
> cause a crash.

Is it worth putting this up as a bug on the gcc bugs database?

Rob

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

- Raw text -