On Thu, 03 May 2001 10:39:23 PDT, Doug MacEachern wrote:
>to solve, STORE would need to make sure the value is already solar tied or
>take care to tie it, so that access to references such as $h->{two} are
>also serialized. if %$h contains values which are references, they
>must also be solar, which means walking the entire value structure
>for each STORE. ugh.
If and only if the value being stored is not already solar. I don't
think that's too bad.
>then of course there's more problems with certain structures, such as CV,
>which cannot share padlists across interpreters without duping the CV or
>pp_entersub becoming aware and locking the CV.
I don't see a _need_ for solar CVs, given that the optrees are already
shared, thanks to them being readonly.
Sarathy
[EMAIL PROTECTED]
- Re: our :shared $foo / iThreads Alan Burlison
- Re: our :shared $foo / iThreads Benjamin Sugars
- Re: our :shared $foo / iThreads Chris Stith
- Re: our :shared $foo / iThreads Alan Burlison
- Re: our :shared $foo / iThreads Chris Stith
- Re: our :shared $foo / iThreads Alan Burlison
- Re: our :shared $foo / iThreads Artur Bergman
- Re: our :shared $foo / iThreads Doug MacEachern
- Re: our :shared $foo / iThreads Gurusamy Sarathy
- Re: our :shared $foo / iThreads Doug MacEachern
- Re: our :shared $foo / iThreads Gurusamy Sarathy
- Re: our :shared $foo / iThreads Artur Bergman
- Re: our :shared $foo / iThreads Dan Sugalski
- Re: our :shared $foo / iThreads Benjamin Sugars
- Re: our :shared $foo / iThreads Dan Sugalski
- Re: our :shared $foo / iThreads Artur Bergman
- Re: our :shared $foo / iThreads Dan Sugalski
- Re: our :shared $foo / iThreads Doug MacEachern
- Re: our :shared $foo / iThreads Artur Bergman
- Re: our :shared $foo / iThreads Doug MacEachern
- Re: our :shared $foo / iThreads Artur Bergman
