J
Jonathan Aldrich
Researcher at Carnegie Mellon University
Publications - 186
Citations - 5019
Jonathan Aldrich is an academic researcher from Carnegie Mellon University. The author has contributed to research in topics: Object-oriented programming & Software system. The author has an hindex of 34, co-authored 186 publications receiving 4778 citations. Previous affiliations of Jonathan Aldrich include California Institute of Technology & University of Washington.
Papers
More filters
Proceedings ArticleDOI
ArchJava: connecting software architecture to implementation
TL;DR: A case study applying ArchJava to a circuit-design application suggests that ArchJava can express architectural structure effectively within an implementation, and that it can aid in program understanding and software evolution.
Proceedings ArticleDOI
Alias annotations for program understanding
TL;DR: AliasJava is presented, a capability-based alias annotation system for Java that makes alias patterns explicit in the source code, enabling developers to reason more effectively about the interactions in a complex system.
Book ChapterDOI
Open modules: modular reasoning about advice
TL;DR: Open Modules as discussed by the authors is a formal model for reasoning about the equivalence of programs under advice, which can be used to show that clients are unaffected by semantics-preserving changes to a module's implementation.
Proceedings ArticleDOI
Modular typestate checking of aliased objects
Kevin Bierhoff,Jonathan Aldrich +1 more
TL;DR: A sound modular protocol checking approach that allows a great deal of flexibility in aliasing while guaranteeing the absence of protocol violations at runtime, and a novel abstraction, access permissions, that combines typestate and object aliasing information.
Book ChapterDOI
Ownership Domains: Separating Aliasing Policy from Mechanism
Jonathan Aldrich,Craig Chambers +1 more
TL;DR: This paper proposes an ownership type system that is too weak to express many important aliasing constraints, yet also so restrictive that they prohibit many useful programming idioms.