Inheritance-Based Subtyping

Fisher, Kathleen; Reppy, John

doi:10.1006/inco.2002.3169

Cited by 5 publications

(1 citation statement)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Subtyping and type equality for object types are structural (though [FiR00] proposes to add nominal class types as well). Moby has no downcasting or type case mechanism for dynamically dispatching on the class of an object, but hierarchical, extensible datatypes (inspired by the object types of OML) can be used to tag objects and then programs can dispatch on these tags.…”

Section: F ω < -Based Language Designsmentioning

confidence: 99%

Should ML be Object-Oriented?

MacQueen

2002

Form. Asp. Comput.

View full text Add to dashboard Cite

Abstract.At a fundamental level, functional and object-oriented programming languages are all 'higherorder', in the sense that they support computing with values that are themselves pieces of program code encapsulated with a local environment. In functional languages these 'active' values are functions, while in object-oriented languages they are objects. Both styles of higher-order language claim to provide good support for writing adaptable programs, but functional and object-oriented languages achieve this adaptability in different ways: functional programs rely on parameterisation at the value, type and module level, while object-oriented languages rely primarily on subtyping and implementation inheritance. Here we compare these two approaches, mainly in terms of the features and properties of their type systems, and consider the benefits and disadvantages of unifying (or merging) the two paradigms by adding object-oriented features to ML as a base language. We argue that while some of the simpler aspects of object-oriented languages are compatible with ML, adding a full-fledged class-based object system to ML leads to an excessively complex type system and relatively little expressive gain, especially if we aim to preserve that mostly functional style of programming that is a major advantage of ML.

show abstract

Section: F ω < -Based Language Designsmentioning

confidence: 99%

Should ML be Object-Oriented?

MacQueen

2002

Form. Asp. Comput.

View full text Add to dashboard Cite

show abstract

On Traits and Types in a Java-like Setting

Bono

Damiani

Giachino

Fifth Ifip International Conference on Theoretical Computer Science – TCS 2008

View full text Add to dashboard Cite

Both single and multiple class-based inheritance are often inappropriate as a reuse mechanism, because classes play two competing roles. Namely, a class is both a generator of instances and a unit of reuse. Traits are composable pure units of behavior reuse, consisting only of methods, that have been proposed as an add-on to single class-based inheritance in order to improve reuse. However, adopting traits as an add-on to traditional class-based inheritance is not enough: classes, besides their primary role of generators of instances, still play the competing role of units of reuse. Therefore, a style of programming oriented to reuse is not enforced by the language, but left to the programmer's skills. Traits have been originally proposed in the setting of dynamically typed language. When static typing is also taken into account, the role of unit of reuse and the role of type are competing, too.We argue that, in order to support the development of reusable program components, object oriented programming languages should be designed according to the principle that each software structuring construct must have exactly one role. We propose a realignment of the class-based object-oriented paradigm by presenting programming language features that separate completely the declarations of object type, behavior and generator. We illustrate our proposal through a core calculus and prove the soundness of the type system w.r.t. the operational semantics.

show abstract

Integrating Nominal and Structural Subtyping

Malayeri

Aldrich

ECOOP 2008 – Object-Oriented Programming

View full text Add to dashboard Cite

Inheritance-Based Subtyping

Cited by 5 publications

References 9 publications

Should ML be Object-Oriented?

Should ML be Object-Oriented?

On Traits and Types in a Java-like Setting

Integrating Nominal and Structural Subtyping

Contact Info

Product

Resources

About