On Tue, Oct 12, 2010 at 3:46 PM, Tim Bunce tim.bu...@pobox.com wrote:
On Tue, Oct 12, 2010 at 03:42:00PM +0200, Leon Timmermans wrote:
On Mon, Oct 11, 2010 at 12:32 AM, Ben Goldberg ben-goldb...@hotmail.com
wrote:
If thread-unsafe subroutines are called, then something like ithreads
might
On Fri, Oct 15, 2010 at 11:04:18AM +0100, Tim Bunce wrote:
On Thu, Oct 14, 2010 at 11:52:00PM -0400, Benjamin Goldberg wrote:
From: tim.bu...@pobox.com
So I'd like to use this sub-thread to try to identify when lessons we
can learn from ithreads. My initial thoughts are:
Date: Tue, 12 Oct 2010 23:46:48 +0100
From: tim.bu...@pobox.com
To: faw...@gmail.com
CC: ben-goldb...@hotmail.com; perl6-language@perl.org
Subject: Lessons to learn from ithreads (was: threads?)
On Tue, Oct 12, 2010 at 03:42:00PM +0200, Leon Timmermans wrote:
On Mon, Oct 11, 2010 at
On Thu, Oct 14, 2010 at 11:52:00PM -0400, Benjamin Goldberg wrote:
From: tim.bu...@pobox.com
So I'd like to use this sub-thread to try to identify when lessons we
can learn from ithreads. My initial thoughts are:
- Don't clone a live interpreter.
Start a new
Earlier, Leon Timmermans wrote:
: * Code sharing is actually quite nice. Loading Moose separately in a
: hundred threads is not. This is not trivial though, Perl being so
On Fri, Oct 15, 2010 at 10:56 AM, Tim Bunce tim.bu...@pobox.com wrote:
...
Another important issue here is portability of concepts across
implementations of perl6. I'd guess that starting a thread with a fresh
interpreter is likely to be supportable across more implementations than
starting a
On Wed, Oct 13, 2010 at 1:13 PM, Tim Bunce tim.bu...@pobox.com wrote:
If you wanted to start a hundred threads in a language that has good
support for async constructs you're almost certainly using the wrong
approach. In the world of perl6 I expect threads to be used rarely and
for specific
On Wed, Oct 13, 2010 at 04:00:02AM +0200, Leon Timmermans wrote:
On Wed, Oct 13, 2010 at 12:46 AM, Tim Bunce tim.bu...@pobox.com wrote:
So I'd like to use this sub-thread to try to identify when lessons we
can learn from ithreads. My initial thoughts are:
- Don't clone a live interpreter.
On Wed, Oct 13, 2010 at 12:46 AM, Tim Bunce tim.bu...@pobox.com wrote:
So I'd like to use this sub-thread to try to identify when lessons we
can learn from ithreads. My initial thoughts are:
- Don't clone a live interpreter.
Start a new thread with a fresh interpreter.
- Don't try to
