Comments on: matching Erlang’s receive semantics http://thatmattbone.com/2008/07/matching-erlangs-receive-semantics/ Tue, 29 Jun 2010 15:23:44 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Matt Bone http://thatmattbone.com/2008/07/matching-erlangs-receive-semantics/comment-page-1/#comment-25 Matt Bone Wed, 09 Jul 2008 17:15:00 +0000 http://thatmattbone.com/?p=44#comment-25 The early versions of receive() I had done just blocked for any message and then discarded that message if it did not match. <br/><br/>The current version behaves like Erlang. Receive blocks until a message that matches is found. The non-matching messages remain in the process mailbox for future receive() calls that may be able to match against them. The early versions of receive() I had done just blocked for any message and then discarded that message if it did not match.

The current version behaves like Erlang. Receive blocks until a message that matches is found. The non-matching messages remain in the process mailbox for future receive() calls that may be able to match against them.

]]> By: Faré http://thatmattbone.com/2008/07/matching-erlangs-receive-semantics/comment-page-1/#comment-24 Faré Wed, 09 Jul 2008 04:00:00 +0000 http://thatmattbone.com/?p=44#comment-24 Can you elaborate on this semantic issue? <br/><br/>I don't understand what you're trying to do and what the issue is. Can you elaborate on this semantic issue?

I don’t understand what you’re trying to do and what the issue is.

]]>