On Sat, 26 Aug 2000, Steven W McDougall wrote:
> However, the distinction between compile time and run time that it
> relies on doesn't exist in Perl. For example, if we chase through
> perlfunc.pod a bit, we find
No? I'll admit that it may run through the compile and run modes
multiple times, b
>> Users can (and do) write open code in modules.
> I don't understand. Do you think that needs to be prevented?
No, I just want to know what happens when they do it.
Let's look at an example.
1. Non-threaded
#!/usr/local/bin/perl
sub foo { print 1 }
foo();
eval 'sub foo { pr
A couple of other scenerios
Thread 1Thread 2
push(@a, @b); $a[35]++
User level cross variable consistancy.
push(@a, $b);
$acount++ if $b <35;
Even cooperative threading doesn't help.
> "SWM" == Steven W McDougall <[EMAIL PROTECT
Thread shared variables will have to be declared.
Perhaps
my $foo :shared;
Otherwise, the variable refers to thread specific storage.
Up for grabs is what the variable contains upon thread start. undef
or a copy-on-write version of the original.
> "SWM" == Steven W McDougall <[EM
