Which comes first: the object or the class? Language designers enjoy the conceptual simplicity of object-based languages (such as Emerald or Self) while many programmers prefer the pragmatic utility of classical inheritance (such as Simula and Java). Programmers in object-based languages have a tendency to build libraries to support traditional inheritance, and language implementations are often contorted to the same end. In this paper, we revisit the relationship between classes and objects. We model various kinds of inheritance in the context of an object-oriented language whose objects are not defined by classes, and explain why class inheritance and initialisation cannot be easily modelled purely by delegation.
Thu 21 Jul
|15:30 - 15:55|
Timothy JonesVictoria University of Wellington, Michael HomerVictoria University of Wellington, James NobleVictoria University of Wellington, Kim BrucePomona CollegeLink to publication DOI Pre-print Media Attached
|15:55 - 16:20|
|Link to publication DOI Pre-print Media Attached|
|16:20 - 16:45|
Casper Bach PoulsenTU Delft, Pierre NeronFrench Network and Information Security Agency (ANSSI), Andrew TolmachPortland State University, Eelco VisserDelft University of TechnologyLink to publication DOI Pre-print Media Attached