Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Walter L. Hill

dblp:64/6135 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
0since 2021 · last 1990
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2Artificial intelligence and machine learning · 1 · 1 first-authorGraphics, computer vision, multimedia, augmented reality and games · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
3 papers
Programming languages and type systems · 83% Software maintenance and evolution · 17%

Topics — the 4 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Programming languages and type systems › type systems
subtyping
0.011990
Inheritance Is Not Subtyping · POPL 1990
Programming languages and type systems
type systems
0.011990
Inheritance Is Not Subtyping · POPL 1990
Software maintenance and evolution
software reuse
0.011987
Machine Learning for Software Reuse · IJCAI 1987
Programming languages and type systems
inheritance
0.011989
Interfaces for Strongly-Typed Object-Oriented Programming · OOPSLA 1989

Methods — techniques the papers use, named apart from their topics

polymorphism · 0.0machine learning · 0.0
YearPublicationVenuePosition
1990 Inheritance Is Not Subtyping
abstract
In typed object-oriented languages the subtype relation is typically based on the inheritance hierarchy. This approach, however, leads either to insecure type-systems or to restrictions on inheritance that make it less flexible than untyped Smalltalk inheritance. We present a new typed model of inheritance that allows more of the flexibility of Smalltalk inheritance within a statically-typed system. Significant features of our analysis are the introduction of polymorphism into the typing of inheritance and the uniform application of inheritance to objects, classes and types. The resulting notion of type inheritance allows us to show that the type of an inherited object is an inherited type but not always a subtype.
William R. Cook, Walter L. Hill, Peter S. Canning
POPL2
1989 Interfaces for Strongly-Typed Object-Oriented Programming
abstract
This paper develops a system of explicit interfaces for object-oriented programming. The system provides the benefits of module interfaces found in languages like Ada and Modula-2 while preserving the expressiveness that gives untyped object-oriented languages like Smalltalk their flexibility. Interfaces are interpreted as polymorphic types to make the system sufficiently powerful. We use interfaces to analyze the properties of inheritance, and identify three distinct kinds of inheritance in object-oriented programming, corresponding to objects, classes, and interfaces, respectively. Object interfaces clarify the distinction between interface containment and inheritance and give insight into limitations caused by equating the notions of type and class in many typed object-oriented programming languages. Interfaces also have practical consequences for design, specification, and maintenance of object-oriented systems.
Peter S. Canning, William R. Cook, Walter L. Hill, Walter G. Olthoff
OOPSLA3
1987 Machine Learning for Software Reuse
Walter L. Hill
IJCAI1