> I think there may be a necessity for more than just a work area to be > non-shared. There has been no meaningful discussion so far related to > the fact that the vast majority of perl6 modules will *NOT* be threaded, > but that people will want to use them in threaded programs. That is a > non-trivial problem that may best be solved by keeping the entirety of > such modules private to a single thread. In that case the optree might > also have to be private, and with that and private work area it looks > very much like a full interpreter to me. RFC 1 proposes this model, and there was some discussion of it on perl6-language-flow. RFC 178 argues against it, under DISCUSSION, Globals and Reentrancy. - SWM
- Re: RFC 178 (v2) Lightweight ... Chaim Frenkel
- Re: RFC 178 (v2) Lightweight ... Alan Burlison
- Re: RFC 178 (v2) Lightweight ... Chaim Frenkel
- Re: RFC 178 (v2) Lightweight ... Alan Burlison
- Re: RFC 178 (v2) Lightweight ... Steven W McDougall
- Re: RFC 178 (v2) Lightweight ... Steven W McDougall
- Re: RFC 178 (v2) Lightweight ... Chaim Frenkel
- Re: RFC 178 (v2) Lightweight ... Nick Ing-Simmons
- Re: RFC 178 (v2) Lightweight ... Chaim Frenkel
- Re: RFC 178 (v2) Lightweight ... Alan Burlison
- Re: RFC 178 (v2) Lightweight ... Steven W McDougall
- Re: RFC 178 (v2) Lightweight ... Bryan C . Warnock
- Re: RFC 178 (v2) Lightweight ... Steven W McDougall
- Re: RFC 178 (v2) Lightweight ... Nick Ing-Simmons
- Re: RFC 178 (v2) Lightweight ... raptor
- Re: RFC 178 (v2) Lightweight ... Chaim Frenkel
- Re: RFC 178 (v2) Lightweight Threads Glenn King
- Re: RFC 178 (v2) Lightweight Threads Jarkko Hietaniemi
- Re: RFC 178 (v2) Lightweight Threads Alan Burlison