However, the region of mutual exclusion can have holes so that
* activities can be suspended and later resumed
* other activities can use the region of mutual
exclusion while a message is being processed by
another Actor
For example, a readers/writer scheduler for a database must be processing multiple activities concurrently, which is very difficult to implement in Erlang.
Might be? Of course we can. Obviously infinite objects are irrelevant to modeling the real world. They are just a shorthand for adding a bunch of annoying qualifiers to every mathematical statement.
> Obviously infinite objects are irrelevant to modeling the real world.
I disagree. The concept of infinite objects are essentially object sets with an unknown limit. This represents a general case from which we can draw important concepts.
Are you saying that the Erlang VM enforces mutual exclusion within its Actors, and that mutual exclusion should not be enforced within Actors?