[erlang-questions] Shared memory and message passing

[Robert Virding]

I agree with Joe, the Erlang implementation can use whatever mechanisms 
it likes just as long as the semantics are unchanged. Actually this is 
no problem as Erlang does not allow updating of data. Single heap memory 
models never copy data from one process to another, they just pass the 
reference. Sending messages is an O(1) operation.

Robert

Joe Armstrong (TN/EAB) wrote:
> This kind of usage is, I guess OK, if it's hidden from the
> user as part of an language implementation, but it should
> definitely not be exposed to the application programmer.
> 
> It's rather like garbage collection - or page table manipulation
> ok for a very small number of system programmers to use, but
> forbidden in regular applications
> 
> /Joe
> 
> 
>>-----Original Message-----
>>From: Joel Reymont [mailto:joelr1@REDACTED] 
>>Sent: den 5 september 2006 11:02
>>To: Joe Armstrong (TN/EAB)
>>Cc: erlang-questions@REDACTED
>>Subject: Shared memory and message passing
>>
>>Joe,
>>
>>What about using shared memory to optimize message passing 
>>and avoid copying memory?
>>
>>This does not involve locks or critical sections, right?
>>
>>	Thanks, Joel
>>
>>--
>>http://wagerlabs.com/
>>
>>
>>
>>
>>
>>
> 
> 
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>