Classification of actor languages
Tom Van Cutsem <[email protected]> Fri, 13 Feb 2015 20:06:17 +0100
| Newsgroups | gmane.comp.lang.e.general |
|---|---|
| Message-ID | <CAKDfNj95kioH27=-CGvjoJ4sjaT_8QV8v15ZQ36oVtXfM9=MKQ@mail.gmail.com> |
--===============8213442879070406357== Content-Type: multipart/alternative; boundary=047d7b6da9c661a9ba050efcee87 --047d7b6da9c661a9ba050efcee87 Content-Type: text/plain; charset=UTF-8 [cross-posting on e-lang and friam as the content is relevant to E yet most activity seems to be going on on the friam list these days] Hi, Joeri De Koster, a PhD student of mine who recently graduated, did a survey on actor languages and systems which I think may be of interest to this audience. See Chapter 2 of his PhD text: http://soft.vub.ac.be/Publications/2015/vub-soft-phd-15-01.pdf There's an at-a-glance summary table on page 47 of the pdf. He compares various actor systems based on the way message reception and internal state changes are expressed, among others. He then clusters the systems into four broad "families". It's by no means an extensive survey, but I believe it does provide some insight into the diversity of actor systems. E's communicating event loop model is singled out as one particular type of actor "family". Interestingly, it's the only one of the four that enables an actor to have multiple public "facets" (think of a "facet" as an object inside a vat that is designated by a far reference). In case you're wondering: the classification isn't the PhD's main contribution. The main contribution is a series of language abstractions called "domains" that enable controlled synchronous access to shared mutable state between communicating event loops (when implemented on shared-memory systems). Best regards, Tom --047d7b6da9c661a9ba050efcee87 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">[cross-posting on e-lang and friam as the content is relev= ant to E yet most activity seems to be going on on the friam list these day= s]<div><br></div><div>Hi,</div><div><br></div><div>Joeri De Koster, a PhD s= tudent of mine who recently graduated, did a survey on actor languages and = systems which I think may be of interest to this audience. See Chapter 2 of= his PhD text:</div><div><br></div><div><a href=3D"http://soft.vub.ac.be/Pu= blications/2015/vub-soft-phd-15-01.pdf">http://soft.vub.ac.be/Publications/= 2015/vub-soft-phd-15-01.pdf</a><br></div><div><br></div><div>There's an= at-a-glance summary table on page 47 of the pdf.</div><div><br></div><div>= He compares various actor systems based on the way message reception and in= ternal state changes are expressed, among others. He then clusters the syst= ems into four broad "families". It's by no means an extensive= survey, but I believe it does provide some insight into the diversity of a= ctor systems.</div><div><br></div><div>E's communicating event loop mod= el is singled out as one particular type of actor "family". Inter= estingly, it's the only one of the four that enables an actor to have m= ultiple public "facets" (think of a "facet" as an objec= t inside a vat that is designated by a far reference).</div><div><br></div>= <div>In case you're wondering: the classification isn't the PhD'= ;s main contribution. The main contribution is a series of language abstrac= tions called "domains" that enable controlled synchronous access = to shared mutable state between communicating event loops (when implemented= on shared-memory systems).</div><div><br></div><div>Best regards,</div><di= v>Tom</div><div><br></div></div> --047d7b6da9c661a9ba050efcee87-- --===============8213442879070406357== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ e-lang mailing list [email protected] http://www.eros-os.org/mailman/listinfo/e-lang --===============8213442879070406357==--