Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date:	Sun, 22 Aug 2004 03:56:43 -0700
From:	Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To:	cygwin AT cygwin DOT com
Subject:	Re: perl threads problems using 20040720 snapshot
Message-ID:	<20040822105643.GA2732@efn.org>
References:	<20040721071836 DOT GA4068 AT efn DOT org> <20040725205108 DOT GA2396 AT efn DOT org>
Mime-Version:	1.0
In-Reply-To:	<20040725205108.GA2396@efn.org>
User-Agent:	Mutt/1.4.1i
Organization:	bs"d
X-IsSubscribed:	yes

On Sun, Jul 25, 2004 at 01:51:08PM -0700, Yitzchak Scott-Thoennes wrote:
> On Wed, Jul 21, 2004 at 12:18:36AM -0700, Yitzchak Scott-Thoennes wrote:
> > When using recent snapshots, perl threads have some problems.  For example:
> > 
> > $ perl 
-we'use threads; threads->new( sub { print "go" } )->join(); <>; print "done"';
> > 
> > Here, when the thread exits (after printing go), the whole process
> > also exits, instead of waiting for terminal input and printing done.
> 
> I am curious to know if this is only me or if others are also seeing it.

This is still a problem with the 20040821 snapshot.  Is there anything I can
do to help resolve this?  Does anyone else have this problem?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -