Mailing-List:	contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT cygwin DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT cygwin DOT com>
List-Help:	<mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	setup and exceptions
Date:	Sat, 27 Apr 2002 10:49:29 +1000
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
Message-ID:	<FC169E059D1A0442A04C40F86D9BA7600C5F26@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:	"Cygwin-Apps" <cygwin-apps AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g3R0ncD19405

Well,
	I've just tried, and exceptions do work. The stdc++ library I've
got here appears to have been built without thread support, so we can't
use cross-thread exceptions. In fact IIRC we can only use exceptions
within a single thread.

This means that some care is needed before we introduce any exception
using code. I'm not sure if gcc needs to be reubuilt if/when threads are
enabled... If the answer is yes, then simply getting a threaded
libstdc++ is not enough.

If the answer is no, and "someone" were to make a prebuilt mingw
libstdc++ available with thread support, then we can use exceptions more
freely.

For the moment, when I get time, I'll review what occurs in each thread,
and what mechanism we might use to safely get some benefits.

i.e. if the only time we have multiple threads is a separate GUI update
thread, then as long as that update thread never creates or absorbs
exceptions, we are safe.

Rob

- Raw text -