2 citations found. Retrieving documents...
Boris Bokowski. Coffeestrainer: Statically-checked constraints on the definition and use of types in java. In Proceedings of ESEC/FSE'99. Springer-Verlag, September 1999.

 Home/Search   Document Details and Download   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Codifying Structural Regularities of Object-Oriented Programs - Wuyts, Mens   (Correct)

....forward chaining could be better. We currently research how to integrate a forward chainer with our approach. A whole range of related work exists that focus on enforcing or constraining the structure of objectoriented programs. For C there is CCEL [15] or Astlog [7] For Java, CoffeeStrainer [3] is a preprocessor that allows to express structural constraints on Java code. Like law governed systems and N eOpus, all these approaches are restricted to constraining the structure of a program but provide little or no support for querying and code generation. Also, because CCEL and ....

Boris Bokowski. Coffeestrainer: Statically-checked constraints on the definition and use of types in java. In Proceedings of ESEC/FSE'99. Springer-Verlag, September 1999.


Confined Types - Bokowski, Vitek (1999)   (22 citations)  Self-citation (Bokowski)   (Correct)

....restrictions do not prevent viewing an object as having an unrestricted supertype. For all practical purposes, confined types should be viewed as enforcing static scoping of dynamic object references. We have implemented a confinement checker for the Java programming language with CoffeeStrainer [2], a framework for static checking of structural constraints on Java programs. This implementation uses Java packages as protection domains. They are well suited for the task as they group logically related classes and provide the basic access control mechanisms that we need. We extend Java with ....

....class from outside (point r10) cannot occur because confined classes are not accessible from outside. 5.7 Summary The above mentioned constraints can be checked statically. Our implementation is based on CoffeeStrainer, a system for statically checking structural constraints on Java programs [2]. An important design goal for these constraints was modular checking. We categorize packages in three groups, confining packages, packages extended by confining packages, and plain packages. For confining packages confined classes must be checked for constraints C1 and C3 C6, all other classes ....

[Article contains additional citation context not shown here]

B. Bokowski. Coffeestrainer: Statically-checked constraints on the definition and use of types in Java. In Proceedings of ESEC/FSE'99, Toulouse, France, Sept. 1999.

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