Circular sector: Difference between revisions
en>EmausBot m r2.7.2+) (Robot: Adding lb:Kreesausschnëtt |
en>JPaestpreornJeolhlna No edit summary |
||
| Line 1: | Line 1: | ||
'''Ease''' is a general purpose [[parallel computing|parallel]] [[programming language]], designed by [[Steven Ericsson-Zenith]] of [[Yale University]]. It combines the process constructs of [[Communicating sequential processes|CSP]] with logically shared data structures called ''contexts''. Contexts are parallel data types that are constructed by processes and provide a way for processes to interact. | |||
The language includes two process constructors. | |||
A ''cooperation'' includes an explicit barrier synchronization and is written: | |||
::<math>\parallel P() \parallel Q() ;</math> | |||
If one process finishes before the other then it will wait until the other processes are finished. | |||
A ''subordination'' creates a process that shares the ''contexts'' that are in scope when created and finishes when complete (it does not wait for other processes) and is written: | |||
::<math>\big /\!\!/ P() ;</math> | |||
Subordinate processes stop if they attempt to interact with a ''context'' that has completed because the parent process has stopped. This enables speculative processes to be created that will finish if their result is not needed. | |||
Powerful ''replication'' syntax allows multiple processes to be created. For example | |||
::<math>\parallel {i}\; {for}\; {n} : P(i) ;</math> | |||
creates ''n'' synchronized processes each with a local constant ''i''. | |||
Processes cannot share ''local'' variables and cooperate in the construction of shared ''contexts.'' Certain context types, called ''resources'', ensure call-reply semantics. | |||
There are four functions upon contexts: | |||
* '''read''' ( context, variable ), copies a value from the shared ''context'' to the ''variable''. | |||
* '''write''' ( context, expression ), copies the value of ''expression'' to the shared ''context''. | |||
* '''put''' ( context, name ), moves the value bound to ''name'' to the shared ''context''. The value of ''name'' is subsequently ''undefined''. | |||
* '''get''' ( context, name ), moves a value from ''context'' and binds it to ''name''. The value is removed from the context. | |||
Context types are ''Singletons'', ''Bags'' or ''Streams'' and can be subscripted arrays. | |||
Ease has a ''semiotic definition.'' This means that it takes into account the effect the language has on the programmer and how they develop algorithms. The language was designed to ''ease'' the development of parallel programs. | |||
== References == | |||
[http://www.amazon.com/Process-Interaction-Models-Steven-Ericsson-Zenith/dp/1463777914/ Steven Ericsson-Zenith, "Process Interaction Models" (The Ease Language Specification)] | |||
[http://books.google.com/books/about/An_implementation_of_the_Ease_programmin.html?id=8GssNAAACAAJ John Redman, An Implementation of the Ease Programming Language, University of Western Australia, 1991] | |||
[http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=590304 T.H. MacKenzie, T.I. Dix, "A distributed memory multiprocessor implementation of C-with-Ease," IEEE International Conference on Parallel and Distributed Systems, 2002] | |||
[http://doi.ieeecomputersociety.org/10.1109/ICPADS.1998.741145 T.H. MacKenzie, T.I. Dix, "Object-Oriented Ease-Based Parallel Primitives in C++," icpads, p. 623, 1998 International Conference on Parallel and Distributed Systems (ICPADS'98), 1998] | |||
[[Category:Concurrent programming languages]] | |||
[[Category:Concurrency control]] | |||
{{compu-lang-stub}} | |||
Revision as of 10:23, 7 April 2013
Ease is a general purpose parallel programming language, designed by Steven Ericsson-Zenith of Yale University. It combines the process constructs of CSP with logically shared data structures called contexts. Contexts are parallel data types that are constructed by processes and provide a way for processes to interact.
The language includes two process constructors.
A cooperation includes an explicit barrier synchronization and is written:
If one process finishes before the other then it will wait until the other processes are finished.
A subordination creates a process that shares the contexts that are in scope when created and finishes when complete (it does not wait for other processes) and is written:
Subordinate processes stop if they attempt to interact with a context that has completed because the parent process has stopped. This enables speculative processes to be created that will finish if their result is not needed.
Powerful replication syntax allows multiple processes to be created. For example
creates n synchronized processes each with a local constant i.
Processes cannot share local variables and cooperate in the construction of shared contexts. Certain context types, called resources, ensure call-reply semantics.
There are four functions upon contexts:
- read ( context, variable ), copies a value from the shared context to the variable.
- write ( context, expression ), copies the value of expression to the shared context.
- put ( context, name ), moves the value bound to name to the shared context. The value of name is subsequently undefined.
- get ( context, name ), moves a value from context and binds it to name. The value is removed from the context.
Context types are Singletons, Bags or Streams and can be subscripted arrays.
Ease has a semiotic definition. This means that it takes into account the effect the language has on the programmer and how they develop algorithms. The language was designed to ease the development of parallel programs.
References
Steven Ericsson-Zenith, "Process Interaction Models" (The Ease Language Specification)
Hello!
My name is Marguerite and I'm a 29 years old boy from New Haven.
My web-site; http://www.hostgator1centcoupon.info