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 variables will be known to the core at runtime, in the threaded hash structure itself. Any variable that has a 'per-thread' component should be self-contained. Dan
- RFC 136 (v1) Implementation of hash iterators Perl6 RFC Librarian
- Re: RFC 136 (v1) Implementation of hash iterators David L. Nicol
- Re: RFC 136 (v1) Implementation of hash itera... David L. Nicol
- Re: RFC 136 (v1) Implementation of hash i... Tom Hughes
- Re: RFC 136 (v1) Implementation of hash i... David L. Nicol
- Re: RFC 136 (v1) Implementation of ha... Dan Sugalski
- Re: RFC 136 (v1) Implementation ... David L. Nicol
- Re: RFC 136 (v1) Implementat... Dan Sugalski
- Re: RFC 136 (v1) Impleme... Larry Wall
- Re: RFC 136 (v1) Impleme... Dan Sugalski
- Re: RFC 136 (v1) Impleme... Larry Wall
- Re: RFC 136 (v1) Impleme... Dan Sugalski
- Re: RFC 136 (v1) Impleme... Jeremy Howard
- Re: RFC 136 (v1) Impleme... Tom Hughes
- Re: RFC 136 (v1) Impleme... Chaim Frenkel
- Re: RFC 136 (v1) Implementat... Chaim Frenkel