Safe instantiation in generic Java

Authors:
Eric E. Allen;Robert Cartwright
Affiliations:
Sun Microsystems, Inc.;Rice University
Venue:
Proceedings of the 3rd international symposium on Principles and practice of programming in Java
Year:
2004

Citing 7
Cited 2

Pizza into Java: translating theory into practice

Proceedings of the 24th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
Adding type parameterization to the Java language

Proceedings of the 12th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Making the future safe for the past: adding genericity to the Java programming language

Proceedings of the 13th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Compatible genericity with run-time types for the Java programming language

Proceedings of the 13th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
The case for run-time types in generic Java

PPPJ '02/IRE '02 Proceedings of the inaugural conference on the Principles and Practice of programming, 2002 and Proceedings of the second workshop on Intermediate representation engineering for virtual machines, 2002
Efficient Implementation of Run-time Generic Types for Java

Proceedings of the IFIP TC2/WG2.1 Working Conference on Generic Programming
A theory of mixin modules: basic and derived operators

Mathematical Structures in Computer Science

Component nextgen: a sound and expressive component framework for java

Proceedings of the 22nd annual ACM SIGPLAN conference on Object-oriented programming systems and applications
The Java 5 generics compromise orthogonality to keep compatibility

Journal of Systems and Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper presents the "Safe-Instantiation Principle," a new design principle for evaluating extensions of Java with support for generic types. We discuss the GJ and NextGen formulations of Generic Java and the implications of safe instantiation on both approaches. We then consider the implications of safe-instantiation for the addition of mixins to Java via generic types. Finally, we defend the formulation of mixins as hygienic program constructs, arguing that a hygienic formulation is the only way to maintain safe instantiation and type soundness in Java with mixins, and to prevent the introduction of insidious bugs with no clearly defined point of blame.