Re: Parrot bytecode reentrancy

2005-04-17 Thread Martin D Kealey
On Fri, 15 Apr 2005, Nigel Sandever wrote: > I struck me a while back that there is a contradiction in idea of a shared, > 'my' variable. > > I want to say lexical, but a var declared with 'our' is in some sense lexical. Shared-between-threads and shared-between-scopes are orthogonal properties; u

Re: Parrot bytecode reentrancy

2005-04-15 Thread Nigel Sandever
15/04/2005 10:35:56, Leopold Toetsch <[EMAIL PROTECTED]> wrote: >Nigel Sandever <[EMAIL PROTECTED]> wrote: > >> When a sub that closes over a variable > >> my $closure = 0; >> sub do_something { >> return $closure++: >> } > >> is called from two threads, do the threads

Re: Parrot bytecode reentrancy

2005-04-15 Thread Leopold Toetsch
Nigel Sandever <[EMAIL PROTECTED]> wrote: > When a sub that closes over a variable > my $closure = 0; > sub do_something { > return $closure++: > } > is called from two threads, do the threads share a single closure or > each get their own separate closure? AFAIK

Re: Parrot bytecode reentrancy

2005-04-15 Thread Nigel Sandever
On Thu, 31 Mar 2005 21:17:39 -0500, [EMAIL PROTECTED] (MrJoltCola) wrote: > At 05:57 PM 3/31/2005, Nigel Sandever wrote: > >Is Parrot bytecode reentrant? > > Yes. > > >That is, if I want to have two instances of a class in each of two > >threads, will > >the bytecode for the class need to be lo

Re: Parrot bytecode reentrancy

2005-03-31 Thread MrJoltCola
At 05:57 PM 3/31/2005, Nigel Sandever wrote: Is Parrot bytecode reentrant? Yes. That is, if I want to have two instances of a class in each of two threads, will the bytecode for the class need to be loaded twice? No, just once. Also, will it be possible to pass objects (handles/references) between