Proposal: E / Erlang integration
Wed Jun 7 15:47:39 CEST 2006
On 2006-06-06 06:25, Michael FIG wrote:
> In my mind, the only things that would need to be changed in Erlang in order to support E's semantics would be syntax to send E-style messages (that result in a promise), a construct to invoke code when promises are fulfilled, and a flag to indicate that a specific process is untrusted and may only interact with the rest of the system by receiving and sending E-style messages.
presumably this only shows my ignorance, but i hope that it will be
possible to reduce it after this question :-)
why do erlang need a special syntax to send e-style messages? what does
this add that the normal send (!) does not have?
why do erlang need a special syntax to receive e-style messages? what
does this add that the normal receive does not have?
EPO guidelines 1978: "If the contribution to the known art resides
solely in a computer program then the subject matter is not
patentable in whatever manner it may be presented in the claims."
More information about the erlang-questions