Report on the programming language Euclid

Lampson, Butler; Horning, James J.; London, Ralph L.; Mitchell, James G.; Popek, Gerald J.

doi:10.1145/954666.971189

Cited by 290 publications

(55 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Note that Queue is a "sequential" data type since the operations on an instance should not be executed concurrently; a synchronized queue that may be shared by processes is given later. Also note that the structure of this resource is very similar to the structure one would find in languages such as Modula-2, Euclid [26], and Ada [l]. The actual forms of declarations and statements are somewhat different, however, for reasons mostly having to do with our goal of integrating the sequential and concurrent mechanisms of SR.…”

mentioning

confidence: 87%

An overview of the SR language and implementation

Andrews

Coffin

Elshoff

et al. 1988

ACM Trans. Program. Lang. Syst.

137

View full text Add to dashboard Cite

SR is a language for programming distributed systems ranging from operating systems to application programs. On the basis of our experience with the initial version, the language has evolved considerably. In this paper we describe the current version of SR and give an overview of its implementation. The main language constructs are still resources and operations. Resources encapsulate processes and variables that they share; operations provide the primary mechanism for process interaction. One way in which SR has changed is that both resources and processes are now created dynamically. Another change is that inheritance is supported. A third change is that the mechanisms for operation invocation-call and send-and operation implementation-proc and in-have been extended and integrated. Consequently, all of local and remote procedure call, rendezvous, dynamic process creation, asynchronous message passing, multicast, and semaphores are supported. We have found this flexibility to be very useful for distributed programming. Moreover, by basing SR on a small number of well-integrated concepts, the language has proved easy to learn and use, and it has a reasonably efficient implementation.

show abstract

mentioning

confidence: 87%

An overview of the SR language and implementation

Andrews

Coffin

Elshoff

et al. 1988

ACM Trans. Program. Lang. Syst.

137

View full text Add to dashboard Cite

show abstract

“…Most prominent of which is the Eiffel language but also includes other languages such as Euclid [10], Alphard [11], Anna [12] and SR 0 [13]. Unfortunately, most of the languages that have built-in design contracts are not widely used.…”

Section: Various Implementations Of Design Contractmentioning

confidence: 99%

“….addGroup(jPanel2Layout.createSequentialGroup() .addGap (10,10,10) .addComponent(jLabel8)) .addGroup(jPanel2Layout.createSequentialGroup()…”

Section: Related) Addcomponent(jlabel9)mentioning

confidence: 99%

FOZCIL: A framework for converting formal specifications in Object-Z to design contracts in OO programming languages

George

Zhang

Radimsky

2011

2011 IEEE International Conference on Information Reuse &Amp; Integration

View full text Add to dashboard Cite

Formal languages use mathematical notations to capture the software specifications precisely. Design by Contract is a technique used during software implementation to ensure that the software conforms to the specifications. However, there is a semantic gap in the development process between the specifications written in a formal language and the design contracts written in an implementation language.Automated conversion of formal specifications to the design contracts in object-oriented implementation languages can help bridge this gap. Prior work has been done by Sowmiya Ramkarthik and Sherri Sanders to develop such tools for the automated conversions from the Object-Z formal language to the Java and Object PERL implementation languages. However, each tool was custom built to work with only one v or two such OO languages. Moreover, there has been significant redundant efforts in the development of each of these tools.FOZCIL (Framework for Object Z Conversion to Implementation Language) is a framework that captures and implements these redundant language-independent features as frozen spots (i.e., the fixed part of the framework) and the language-dependent properties as hot spots (i.e., the extensible part of the framework). When the framework accepts the language-dependent features for a target object-oriented language, it generates a FOZCIL tool instance which, in turn, is capable of accepting Object-Z specifications and converting the specifications to skeletal code with dynamicallycheckable design contracts written in that target language.

show abstract

“…Euclid [41] is one of the first languages that considered the problem of aliasing. [37] stressed the need for better treatment of aliasing in object-oriented programs.…”

Section: Related Workmentioning

confidence: 99%

Ownership types for object encapsulation

Boyapati

Liskov

Shrira

2003

Proceedings of the 30th ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages

153

140

View full text Add to dashboard Cite

Ownership types provide a statically enforceable way of specifying object encapsulation and enable local reasoning about program correctness in object-oriented languages. However, a type system that enforces strict object encapsulation is too constraining: it does not allow efficient implementation of important constructs like iterators. This paper argues that the right way to solve the problem is to allow objects of classes defined in the same module to have privileged access to each other's representations; we show how to do this for inner classes. This approach allows programmers to express constructs like iterators and yet supports local reasoning about the correctness of the classes, because a class and its inner classes together can be reasoned about as a module. The paper also sketches how we use our variant of ownership types to enable efficient software upgrades in persistent object stores.

show abstract

Report on the programming language Euclid

Abstract: This report describes a new programming language called Euclid, intended for the expression of system programs which are to be verified.

Cited by 290 publications

References 13 publications

An overview of the SR language and implementation

An overview of the SR language and implementation

FOZCIL: A framework for converting formal specifications in Object-Z to design contracts in OO programming languages

Ownership types for object encapsulation

Contact Info

Product

Resources

About