Translucid contracts for modular reasoning about aspect-oriented programs

Bagherzadeh, Mehdi; Rajan, Hridesh; Leavens, Gary T.; Mooney, Sean L.

doi:10.1145/1869542.1869596

Cited by 1 publication

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Leavens, I helped developed the notion of translucid contracts [6,7] that are a greybox specification mechanism for reasoning about implicit invocation systems [29,44]. We showed that translucid contracts enabled modular reasoning about these kinds of systems, which was thought to be a challenge.…”

Section: Translucid Contractsmentioning

confidence: 99%

“…7 shows a simple class and its corresponding duck future.Translating a system to Java Translating a system to Java is much simpler than translating a capsule to Java. A system is the sole entry point for a Panini program and it is translated into a single class with the public static void main(String []) method needed to make the class executable in a JVM.Figure 2.8 shows a basic system and its corresponding translation into Java.…”

mentioning

confidence: 99%

See 1 more Smart Citation

A unified design of capsules

Mooney

View full text Add to dashboard Cite

The process of reading, writing, and reasoning about concurrent programs benefits from better abstractions for concurrency than what many common languages, such as Java, offer. Capsule-oriented programming and the Panini language utilize the idea of combining state and control within a linguistic mechanism along with asynchronous message passing to provide sequentially trained programmers with an actor-like language that preserves the expected sequential semantics. The initial design of the Panini language splits the world into two distinct elements-capsules and systems. A capsule acts as the unit of both modularity and concurrency in the program. A system acts as the sole point of composition for capsule instances. The problem is that the dichotomy between systems and capsules leads to uncomposable and non-modular programs. The connections between capsule instances in a system declaration are fixed at exactly one point and all capsules instances in program must be declared and connected to each other at a single block of code. This thesis will explore the implications on modularity and reuse of systems when a basic design decision-separating capsules and systems-is relaxed to allow a capsule to declare an internal composition of other capsule instances. Address search(String name); 4 } 5 capsule CSVBook(File file) implements Book { ... } 6 capsule ISUBook implements Book { ... } 7 capsule Search(Book[] books) { 8 List

search(String name) {

show abstract

Section: Translucid Contractsmentioning

confidence: 99%

mentioning

confidence: 99%