| BOYAPATI, C., AND RINARD, M. A parameterized type system for race-free Java programs. In OOPSLA'01 [17], pp. 56--69. |
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Proceedings of the 16th Annual Conference on Object-Oriented Programming Systems, Languages and Applications, Tampa Bay, FL, Oct. 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
....within a single subsystem, or a single result for each method. Our implementation currently produces a separate result for each distinct instantiation of token variable and subsystem values. 6. 4 Ownership Types Ownership type systems are designed to enforce object encapsulation properties [10, 7, 6, 9, 2]. In this capacity, they can be used to ensure that objects from one instance of an abstraction are not used to inappropriately communicate with With the possible exception of timing channels. 25 other instances of the same abstraction [5, 2] For example, one might use ownership types in a ....
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. Tampa Bay, Florida, Oct. 2001.
....provide safe region based memory management for other real time languages as well. Our system makes several important technical contributions over previous type systems for region based memory management. For object oriented programs, it combines region types [16, 23, 34, 42] and ownership types [10, 11, 14, 18, 19] in a unified type system framework. Region types statically ensure that programs never follow dangling references. Ownership types statically enforce object encapsulation and enable modular reasoning about program correctness in object oriented programs. Consider, for example, a Stack object s ....
....garbage collector, then a realtime thread entering the region might have to wait for an unbounded amount of time. Our type system statically ensures that this priority inversion problem cannot happen. Finally, we note that ownership based type systems have also been used for preventing data races [14] and deadlocks [10] for supporting modular software upgrades in persistent object stores [13] for modular specification of e#ects clauses in the presence of subtyping [11, 14] so they can be used as an alternative to data groups [36] and for program understanding [3] We are currently ....
[Article contains additional citation context not shown here]
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
....functions to satisfy the conditions. If even triggers are insucient, we use versions but only in the few cases where they are needed. The upgrade system can statically determine whether transform functions are well behaved if the programming language is extended to support ownership types [11, 12, 14, 15, 24, 25]; we sketch such an extension in the appendix. Ownership types o er a promising approach for making objectoriented programs more reliable, and we think that they will become part of future object oriented languages. However, in the absence of ownership types, the system has to depend on either ....
....objects x encapsulates, then our system provides good semantics without using versions: E. TF(x) can only use x and objects that x encapsulates. Condition E can be checked by a compiler provided the programming language is extended to support ownership types and e ects clauses. Ownership types [11, 12, 14, 15, 24, 25] are used to declare dependencies: if an object x depends on y, x s class will declare that x owns y. The ownership type system will then guarantee that y cannot be accessed from outside of x, i.e. by objects that x doesn t own directly or transitively. E ects clauses [44] allow the compiler to ....
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
....Java, which is an extension to Java that uses ownership types to guarantee the absence of data races and deadlocks in well typed programs. Our approach is JVM compatible: our implementation translates programs to bytecodes that can be run on regular JVMs. 1 Introduction Ownership types [3, 4, 6, 10, 11] provide a statically enforceable way of specifying object encapsulation. The idea is that an object can own subobjects that it depends on, thus preventing them from being accessible outside. Object encapsulation enables local reasoning about program correctness in object oriented programs. ....
....The idea is that an object can own subobjects that it depends on, thus preventing them from being accessible outside. Object encapsulation enables local reasoning about program correctness in object oriented programs. Ownership based type systems have also been used for preventing data races [6] and deadlocks [3] in multithreaded programs, for preventing memory errors in programs that use region based memory management [7] for supporting modular software upgrades in persistent object stores [5] for modular speci cation of e ects clauses in the presence of subtyping [4, 6, 10] so they ....
[Article contains additional citation context not shown here]
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 2001.
No context found.
BOYAPATI, C., AND RINARD, M. A parameterized type system for race-free Java programs. In OOPSLA'01 [17], pp. 56--69.
No context found.
BOYAPATI, C., AND RINARD, M. A parameterized type system for race-free Java programs. In OOPSLA'01 [33], pp. 56--69.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Proceedings of the 16th Annual Conference on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA'01), pages 56--69, Tampa Bay, FL, 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In 16th Annual Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA'01), 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Proceedings of the ACM Conference on Object- Oriented Programming, Systems, Languages and Applications, pages 56--69, 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In OOPSLA 01: Object-Oriented Programming, Systems, Languages, and Applications, pages 56--69. ACM Press, 2001.
No context found.
C. Boyapati, M. Rinard. A parameterized type system for race-free Java programs. In Proc. OOPSLA, pp. 56-69, 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In OOPSLA 01: Object-Oriented Programming, Systems, Languages, and Applications, pages 56--69. ACM Press, 2001.
No context found.
C. Boyapati, M. Rinard. A parameterized type system for race-free Java programs. In Proc. OOPSLA, pp. 56--69, 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In Proceedings of 16th Annual Conference on Object-Oriented Programming, Systems, Languages, and Applications, pages 56-69, October 2001.
No context found.
C. Boyapati and M. Rinard. A parameterized type system for race-free Java programs. In ACM Conference on Object-Oriented Programming, Systems, Languages, and Applications, pages 56--69,
No context found.
C. Boyapati and M. C. Rinard. A parameterized type system for race-free Java programs. In Proc. 16th ACM Conference on Object-Oriented Programming, Systems, Languages and Applications (OOPSLA), volume 36(11) of SIGPLAN Notices, pages 56--69. ACM Press, November 2001.
First 50 documents
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