Abstract
The design of the programming language Oberon was led by the quote by Albert Einstein: ‘make it as simple as possible, but not simpler’. The objective of this paper is to analyze some design solutions and propose alternatives which could both simplify and strengthen the language without making it simpler than possible.
The paper introduces one general concept, the module type, which can be used to represent records, modules, and eventually procedures. Type extension is redefined in terms of component nesting and incomplete designators. As a result, type extension supports multiple inheritance.
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
M. Reiser, N. Wirth: Programming in Oberon. Steps beyond Pascal and Modula. Wokingham: Addison-Wesley 1992
N. Wirth: The Programming Language Oberon. Software — Practice and Experience 18, 671–690 (1988)
N. Wirth: Type Extensions. ACM Transactions on Programming Languages and Systems 10, 204–214 (1987)
H. Moessenboeck, J. Templ: Object Oberon — A Modest Object-Oriented Language. Structured Programming 10, 44–46 (1989)
H. Moessenboeck: The Programming Language Oberon-2 Report. Computer Science Report 160, ETH Zurich 1991
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 1994 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Radenski, A. (1994). Is Oberon as simple as possible? A smaller object-oriented language based on the concept of module type. In: Gutknecht, J. (eds) Programming Languages and System Architectures. Lecture Notes in Computer Science, vol 782. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-57840-4_38
Download citation
DOI: https://doi.org/10.1007/3-540-57840-4_38
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-57840-6
Online ISBN: 978-3-540-48356-4
eBook Packages: Springer Book Archive