| Findler, R. B. and Felleisen, M. (2000). Behavioral interface contracts for java. Technical report, Department of Computer Science, Rice University, Houston. Technical Report CS TR00-366. |
....is a property that must be satisfied by all instances of a class in every stable state. Ei#el s success in DBC contributed to the proliferation of similar notations and tools in many other programming languages, including C [36] 134] 160] C [42] 57] 58] 104] 129] 158] Java [5] 44] [47] [71] 81] 82] 116] 117] NET [3] Python [124] 125] 127] and Smalltalk [20] These notations and tools vary widely in their techniques and approaches to checking assertions at runtime from simple macro preprocessing and compiling to customized class loaders with the on the fly bytecode ....
Robert Bruce Findler and Matthias Felleisen. Behavioral interface contracts for Java. Technical Report CS TR00-366, Department of Computer Science, Rice University, Houston, TX, August 2000.
.... implemented in the programming language Ei el [32 34] Ei el s success in checking pre and postconditions and encouraging the DBC discipline in programming partly contributed to the availability of similar facilities in other programming languages, including C [42] C [12, 16, 39, 46] Java [2, 13, 14, 24, 26], NET [1] Python [38] and Smalltalk [7] These approaches vary widely from a simple assertion mechanism similar to the C assert macros, to full edged contract enforcement capabilities. Among all that we are aware of, however, none uses its assertion checking capability as a basis for automated ....
Robert Bruce Findler and Matthias Felleisen. Behavioral interface contracts for Java. Technical Report CS TR00-366, Department of Computer Science, Rice University, Houston, TX, August 2000.
....for interface specifications. However they don t try to execute the model in isolation or run it in parallel with the implementation. Instead they want to generate black box tests. Besides JML, there has been a lot of work on using assertions to specify Java interfaces, e.g. Contract Java [11, 12], iContract [8] and Jass [4] And of course, Ei#el [23, 24] uses pre and post conditions to specify components. However, these do not introduce model programs as we do. Closer to our work on runtime verification is the work on program checking as proposed by Blum and Wasserman [6] They argue ....
Robert Bruce Findler and Matthias Felleisen. Behavioral interface contracts for java. Technical Report TR00-366, Department of Computer Science, Rice University, August 2000.
No context found.
Findler, R. B. and Felleisen, M. (2000). Behavioral interface contracts for java. Technical report, Department of Computer Science, Rice University, Houston. Technical Report CS TR00-366.
No context found.
Findler, R. B. and Felleisen, M. (2000). Behavioral interface contracts for java. Technical report, Department of Computer Science, Rice University, Houston. Technical Report CS TR00-366.
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