From: Roger Pack <rogerpack2005@...>
Date: 2010-01-06T06:13:16+09:00
Subject: Re: RCR: fork(n) {|n| }

Robert Klemme wrote:
> 2010/1/5 Roger Pack <rogerpack2005@gmail.com>:
>>> I don't think it gains you anything: in a fork the child process has a
>>> completely separate address space, so all variables are independent from
>>> the parent.
>>>
>>> However in threads you may wish explicitly to copy a value, because it
>>> can change in the other thread. Especially;
>>
>> right it doesn't gain anything, except continuity between threading
>> versus forking. �It just surprises me to not allow it.
> 
> How would that proposed change make switching between threads and
> processes easier?  First of all exchanging the function call is not
> sufficient.  You also need to change the communication means between
> different threads / processes. 

Unless you don't do any (ex: sub jobs that used to run in threads can 
now run in processes).
Then you're good (easier: fewer key strokes).

> The only way to make threads and
> processes interchangeable is to create a framework which abstracts all
> these aspects away - which I believe has been done already.  

Anybody know if such a thing exists for ruby?

Thanks!
-r
-- 
Posted via http://www.ruby-forum.com/.