develooper Front page | perl.perl5.porters | Postings from April 2003

Re: 5.8.1@19053: threads goofs

Thread Previous | Thread Next
From:
Ilya Zakharevich
Date:
April 1, 2003 11:48
Subject:
Re: 5.8.1@19053: threads goofs
Message ID:
20030401194729.GE4587@math.berkeley.edu
On Tue, Apr 01, 2003 at 08:56:34PM +0300, Jarkko Hietaniemi wrote:
> >    This is very confusing ("a thread exited"?  Should not they do this
> >    all the time?)  "called exit() or die()ed" should be more clear.
> 
> I'll let Arthur deal with a) as I understand he's working on related
> matters already.  For the b) ... hmmm, how about
> 
> 	A thread terminated when ** other threads were running
> 
> I'm hoping that "terminated" better describes what we mean (namely
> that (an undetached) thread went away without being join()ed, I think...)

But it is not!  The message is printed (IIUC) exactly in the
conditions I wrote above.

> I also think the suggested "called exit() or die()d" is simultaneously
> too verbose and too sparsek: threads can also _exit(), segfault, ...

These would not induce the message.

Hope this helps,
Ilya

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About