This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Implementation of Threads in Perl
=head1 VERSION
Maintainer: Bryan C. Warnock <[EMAIL PROTECTED]>
Date: 01 Aug 2000
Last Modified: 22 Aug 2000
Version: 3
Mailing List: [EMAIL PROTECTED]
> "DLN" == David L Nicol <[EMAIL PROTECTED]> writes:
DLN> "David L. Nicol" wrote:
>> > In perl 6 the keys and values functions should no longer use the
>> > same iterator as the each function - each use of keys and values
>> > should use it's own private iterator instead.
DLN> we
Dan Sugalski wrote:
>
> Any variable that has a 'per-thread' component should be self-contained.
>
> Dan
We don't know how many instances of iteration happening in the
program there will be, or how many there can be. If each instance
of hash iteration
On Tue, 22 Aug 2000, David L. Nicol wrote:
>
> > we could put it in a variable associated with the instance of the
> > keyword. An associative array of threads to current-values.
>
> or in the "global per-thread data area" keyed to some immutable-during-the-run
> value.
Or, since shared varia
> we could put it in a variable associated with the instance of the
> keyword. An associative array of threads to current-values.
or in the "global per-thread data area" keyed to some immutable-during-the-run
value.
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
In message <[EMAIL PROTECTED]>
"David L. Nicol" <[EMAIL PROTECTED]> wrote:
> "David L. Nicol" wrote:
>
> > > In perl 6 the keys and values functions should no longer use the
> > > same iterator as the each function - each use of keys and values
> > > should use it's own private iterator
"David L. Nicol" wrote:
>
> >
> > In perl 6 the keys and values functions should no longer use the
> > same iterator as the each function - each use of keys and values
> > should use it's own private iterator instead.
we could put it in a variable associated with the instance of the
keyword. An
>
> In perl 6 the keys and values functions should no longer use the
> same iterator as the each function - each use of keys and values
> should use it's own private iterator instead.
And a separate one for each thread, too -- can't forget that --
