Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
X-Authentication-Warning:	smtp4.ihug.co.nz: Host animal.ihug.co.nz [203.109.255.132] claimed to be ihug.co.nz
Message-ID:	<3B396FAC.962442C0@ihug.co.nz>
Date:	Wed, 27 Jun 2001 17:31:24 +1200
From:	Ross Smith <ross DOT s AT ihug DOT co DOT nz>
Organization:	Ihug
X-Mailer:	Mozilla 4.76 [en] (X11; U; Linux 2.2.18 i686)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: pthreads works, sorta
References:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF7A0C AT itdomain002 DOT itdomain DOT net DOT au>

Robert Collins wrote:
> 
> What does all this mean? We need to catch invalid memroy access,

Why? A program that passes an invalid thread handle is broken.
Penalising non-broken programs merely to provide better error checking
for broken ones doesn't sound reasonable to me.

-- 
Ross Smith <ross DOT s AT ihug DOT co DOT nz> The Internet Group, Auckland, New Zealand
========================================================================
"Unix has always lurked provocatively in the background of the operating
system wars, like the Russian Army."                  -- Neal Stephenson

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