Oreste : a Reliable Reactive Real-Time Language
The behavior during execution of an Oreste program is driven by the application. To perform reliability, this behavior has to be always defined. The failure of an Oreste’s software component execution is either explicitly recovered, either implicitly propagated to the caller of the component. This is performed by a multi-tasking extension of programming by contract, organized panic and/or resumption proposed for the Eiffel sequential language by B. Meyer.
Unable to display preview. Download preview PDF.
- 1.ISO /TC 184 / SC 2 / WG 4 / N106 ISO /WD 11513.1 Manipuling Industrial Robots, “Programming Languages for Robots” (PLR) Sept. 91.Google Scholar
- 2.B. Meyer, ‘Applying “Design by Contract “, IEEE Computer, pp 40–51, October 1992.Google Scholar
- 3.B. Meyer, “Object-Oriented Software Construction”, Prentice Hall, Englewood Cliffs, N.J., 534p., 1988.Google Scholar
- 4.Le Langage de programmation ADA, Norme AFNOR NF EN 28652, 1989.Google Scholar
- 5.Barbara Liskov, John Guttag, “Abstraction and Specification in Program Development”, MIT Press.Google Scholar
- 7.O.H. Roux, P. Molinaro, “Mécanismes de communication et de synchronisation du langage Temps Reel Oreste”, JJCSIR, Grenoble, France, pp 5–10, 14–16 April 1993.Google Scholar