Re^4: What is PERL_COPY_ON_WRITE Compile Option About

Similar yes, but the difference is how they share memory. Threads, by definition, share memory so that changing a variable in one thread changes the the same variable in all other threads of that process.

Are you're saying that:

1) CoW saves memory when creating new processes by sharing memory until a modification is made to to that part of memory, and

2) CoW prevent threads from sharing modified variables like they normally do?

That seems odd to me.

Comment on Re^4: What is PERL_COPY_ON_WRITE Compile Option About

Replies are listed 'Best First'.
Re^5: What is PERL_COPY_ON_WRITE Compile Option About by hardburn (Abbot) on Mar 04, 2005 at 17:54 UTC
shrug That's all a matter of implementing the thread library for your system. I haven't used Perl Threads much (too buggy for practical use), so I can't comment there, but the details of what "threads" do could change from system to system. "There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.	[reply]
Re^5: What is PERL_COPY_ON_WRITE Compile Option About by BUU (Prior) on Mar 04, 2005 at 21:59 UTC
Similar yes, but the difference is how they share memory. Threads, by definition, share memory so that changing a variable in one thread changes the the same variable in all other threads of that process. I'm not sure where you're getting this, but the perl threads, at least in 5.8, aren't shared by default. Every process gets it's own copy of all of the variables and such, unless you explicitly share them.	[reply]
Re^6: What is PERL_COPY_ON_WRITE Compile Option About by ikegami (Patriarch) on Mar 04, 2005 at 22:29 UTC
By the CoW explanation given earlier in the thread, it would be impossible to share them beyond the point where they change, explicitely or otherwise. One would have to use some form of IPC to share data.	[reply]