On Sun, Feb 01, 2004 at 09:05:03PM +0100, Fredrik (Naranek) Hubinette (Real Build Master) @ Pike (-) developers forum wrote:
That is an option, but you would have all the same issues when sharing data as you would when running each interpreter in a separate process as.
Not really. With threads I've same memory space, with processes - there is no native support of shared memory in Pike (yet), so IPC is slow.
I don't think you understand the issue. Pike has a multitude of internal data structures which have to be protected.
Hmm... This means that I can't create two or more independent Pike interpreters in single process, even without taking into account threads? Everything is global?
Again, I don't think you understand, and I think I would need a whiteboard to explain.
/ Fredrik (Naranek) Hubinette (Real Build Master)
Previous text:
2004-02-01 21:29: Subject: Re: Default backend and thread backends?
On Sun, Feb 01, 2004 at 09:05:03PM +0100, Fredrik (Naranek) Hubinette (Real Build Master) @ Pike (-) developers forum wrote:
That is an option, but you would have all the same issues when sharing data as you would when running each interpreter in a separate process as.
Not really. With threads I've same memory space, with processes - there is no native support of shared memory in Pike (yet), so IPC is slow.
I don't think you understand the issue. Pike has a multitude of internal data structures which have to be protected.
Hmm... This means that I can't create two or more independent Pike interpreters in single process, even without taking into account threads? Everything is global?
Regards, /Al
/ Brevbäraren