Islands: aliasing protection in object-oriented languages
OOPSLA '91 Conference proceedings on Object-oriented programming systems, languages, and applications
Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Ownership types for safe programming: preventing data races and deadlocks
OOPSLA '02 Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
ECCOP '98 Proceedings of the 12th European Conference on Object-Oriented Programming
Observations on the assured evolution of concurrent Java programs
Science of Computer Programming - Special issue: Concurrency and synchronization in Java programs
Dynamic ownership in a dynamic language
Proceedings of the 2007 symposium on Dynamic languages
Verifying correct usage of atomic blocks and typestate
Proceedings of the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications
Practical API Protocol Checking with Access Permissions
Genoa Proceedings of the 23rd European Conference on ECOOP 2009 --- Object-Oriented Programming
A type and effect system for deterministic parallel Java
Proceedings of the 24th ACM SIGPLAN conference on Object oriented programming systems languages and applications
Checking interference with fractional permissions
SAS'03 Proceedings of the 10th international conference on Static analysis
Analyzing security architectures
Proceedings of the IEEE/ACM international conference on Automated software engineering
Proceedings of the 25th European conference on Object-oriented programming
Reim & ReImInfer: checking and inference of reference immutability and method purity
Proceedings of the ACM international conference on Object oriented programming systems languages and applications
Hi-index | 0.00 |
Introduction. Over the last ten years, type systems for reasoning about aliasing have begun to be adopted into mainstream languages and tools. The most obvious benefits came in the area of concurrency, expanding on pioneering work that applied ownership [8], regions [6], and permissions [9,4] to ensure the safety of concurrent programs. However, concurrency alone was insufficient to drive adoption. Aliasing type systems really caught on when researchers found common abstractions that were also useful for other purposes: providing encapsulation [17], enhancing security [7,2], and assisting verification [16,10]-though verification remains a niche application due to the engineering time required to specify and verify code.