The essence of subclassing is the ability to represent classification hierarchies reflecting domain concepts. With the right class mechanism there is no need for a separate type/subtype mechanism, and general classes may have behavior specifications so that subclassing also implies code reuse. Sometimes the application is so well defined (known) that developers may readily start out with classes that represent domain concepts. Singular objects have been around for some time, so a new kind of language with equal support for both objects and classes would simply ask for tool support for objects in the spirit of e.g. Self and support for classes as described above.
Mon 31 Oct Times are displayed in time zone: (GMT+02:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change
|13:30 - 14:05|
Tijs van der StormCWI & University of GroningenPre-print
|14:05 - 14:40|
Benjamin ChungCarnegie Mellon University, Paley LiNortheastern University, Jan VitekNortheastern UniversityPre-print
|14:40 - 15:15|
Ole Lehrmann MadsenAarhus University & The Alexandra Institute, Birger Møller-PedersenUniversity of OsloPre-print