Baker, H. Actor systems for real time computation. Tech. Rept. TR-197, MIT Lab. for Computer Science, Cambridge, Mass., 1978.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....user interface than to that of current Lisp machines. By using a model view controller [4] paradigm we hope to integrate the functionality normally associated with debuggers and inspectors by giving continuations appropriate viewers and controllers. We are also considering the addition of futures [2, 5] to the language, one of the motivations being the possibility of using them as tokens for swapped out objects in an object based virtual memory system. This facility would allow the Macintosh implementation to swap to disk, and give users fine control over paging policies. 9. Conclusion Scheme ....

Baker. H.G. Jr. Actor systems for real-time computation. Tech. Rept. TR-197, MIT Laboratory for Computer Science, Cambridge, MA. March, 1978.

....when an event (i.e. the arrival of a message) takes place. Most of the work on actors has come from MIT though there are others who have adopted the paradigm. Message passing is also present in non actor systems such as Smalltalk and Thoth (see the Gentleman paper) See also Actor languages . [Agha85 Agha86 Bake78 Ferb83 Gent81 Hewi77a Hewi77b Jong86 Zimm84] OIS: Some object oriented modelling of o#ce information systems. Gibb82 Gibb84 Woo85b Woo86] Reliability: Various papers on aspects of reliability, resilience, recovery and fault tolerance. Haer83 Kohl81 Oki83 Shin84 Svob84 Verh78] Security: Security issues for objects seem to be ....

H.G. Baker, "Actor Systems for Real Time Computation", MIT/LCS/TR197, MIT lab for Computer science, 1978.

....case of a parameterized Procedure or Iterator) CLU contains both built in and user defined types. Unlike Smalltalk, however, users are not free to reimplement system types. Internally, CLU uses object descriptors to name objects. 2.1. 5 Actor Languages The actor model [Hewitt 77, Yonezawa 77, Baker, Jr. 78, Agha 86] was developed in an attempt to formalize and synthesize concepts of abstract objects communicating by message passing. Actors generalize the calculus of Church [Church 41] to include concurrency 19 and the effects of parallelism. The development of actor theory was directly influenced ....

....[Church 41] to include concurrency 19 and the effects of parallelism. The development of actor theory was directly influenced by the concepts of Smalltalk. Actor theory is independent of any particular programming language but has been used to examine and analyze both languages and systems [Baker, Jr. 78] In actor theory, active objects called actors influence the behavior of other actors by sending them messages. These objects in turn send more messages. Messages are themselves actors that are created when needed by the sending actor. Actor languages do not support classes, inheritance, or ....

[Article contains additional citation context not shown here]

Henry G. Baker, Jr. Actor Systems for Real-Time Computation. PhD thesis, M.I.T., March 1978. also MIT/LCS/TR-197.

....= 0; the memory allocated might be freed because p does not hold its address directly, rather indirectly. 6.1.2.2 Scavenging Scavenging algorithms have been improved over the last decade, resulting in a significant performance gain in Smalltalk and Lisp systems. Originally, the Baker algorithm [Baker 78] divided the heap in two spaces: ToSpace and FromSpace. When the FromSpace is full, the references are scanned and referenced objects in FromSpace are copied to ToSpace. In systems where references are direct pointers to objects, a forwarding pointer must be left in FromSpace to update further ....

Henry G. Baker. Actor systems for real-time computation. MIT Laboratory for Computer Science, 1978.

....cannot be created by programs as they are running. Processes usually must be explicitly destroyed when no longer needed. Communication between processes takes the form of assignment to memory cells shared between processes. We propose that parallel processes be represented by actors celled futures [Baker and Hewitt 1977]. Futures can be created dynamically and disappear by garbage collection rather than explicit deletion when they re no longer needed. Communication between processes takes place using shared actors called serializers, which protect their internal state against timing errors. In Object Oriented ....

Baker, H., Actor Systems For Real Time Computation, Technical Report 197, MIT Laboratory for Computer Science, 1977.

No context found.

Baker, Henry. Actor Systems for Real-Time Computation. MIT/LCS/TR-197, March 1978.

No context found.

Baker, H. Actor systems for real time computation. Tech. Rept. TR-197, MIT Lab. for Computer Science, Cambridge, Mass., 1978.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC