[erlang-questions] object vs. actor (Re: Massive Numbers of Actors vs. Massive Numbers of Objects vs. ????)
Thu Mar 1 00:04:58 CET 2012
Am 29.02.12 23:26, schrieb Raoul Duke:
> ...ah so one way of looking at it is: when sending a message to an
> actor, the actor is going to get thread on which to process the
> message, whereas an object either needs you to call into it so it can
> get the thread, or you have to do some other more manual work to give
> it a thread.
Yes that is how most object (oriented) systems are implemented today.
But it is more an implementation detail: e.g Simula the grand mother of
object orientation was especially used for simulation an objects could
also be active entities by using coroutines (were control can be
interrupted and later continued thus enabling multi tasking).
> erlang-questions mailing list
More information about the erlang-questions