At 11:59 AM 9/10/00 -0700, Benjamin Stuhl wrote:
--- Chaim Frenkel [EMAIL PROTECTED] wrote:
Now where
sub recursive() { my $a :shared; ; return
recursive() }
would put $a or even which $a is meant, is left as an
excersize
for someone brighter than me.
%P6-E-MEANINGLESS, "my
Steven W McDougall [EMAIL PROTECTED] writes:
1. All threads execute the same op tree
Consider an op, like
fetch(b)
If you actually compile a Perl program, like
$a = $b
and then look at the op tree, you won't find the symbol "$b", or "b"
anywhere in it.
But it isn't
At 10:26 PM 9/9/00 -0400, Steven W McDougall wrote:
RFC 178 proposes a shared data model for Perl6 threads. In a shared
data model
- globals are shared unless localized
- file-scoped lexicals are shared unless the thread recompiles the
file
- block scoped lexicals may be shared by
- passing
--- Chaim Frenkel [EMAIL PROTECTED] wrote:
"SWM" == Steven W McDougall [EMAIL PROTECTED]
writes:
SWM If you actually compile a Perl program, like
SWM $a = $b
SWM and then look at the op tree, you won't find the
symbol "$b", or "b"
SWM anywhere in it. The fetch() op does not
en enough
discussion of it on perl6-internals that we have some understanding of
its performance characteristics. RFCs for other thread models would
allow us to discuss them in definite terms, and come to some
understanding of their performance characteristics, as well. This
would then be a basis fo
"SWM" == Steven W McDougall [EMAIL PROTECTED] writes:
SWM If you actually compile a Perl program, like
SWM$a = $b
SWM and then look at the op tree, you won't find the symbol "$b", or "b"
SWM anywhere in it. The fetch() op does not have the name of the variable
SWM $b; rather, it
SWM If you actually compile a Perl program, like
SWM $a = $b
SWM and then look at the op tree, you won't find the symbol "$b", or "b"
SWM anywhere in it. The fetch() op does not have the name of the variable
SWM $b; rather, it holds a pointer to the value for $b.
Where did you
