Dimensions of object-based language design
Published 1 December 1987Open access
Peter Wegner
Citations515
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
The potential inconsistency of object-oriented sharing and distributed autonomy is discussed, suggesting that compromises between sharing and autonomy will be necessary in designing strongly typed object- oriented distributed database languages.
Abstract
The design space of object-based languages is characterized in terms of objects, classes, inheritance, data abstraction, strong typing, concurrency, and persistence. Language classes (paradigms) associated with interesting subsets of these features are identified and language design issues for selected paradigms are examined. Orthogonal dimensions that span the object-oriented design space are related to non-orthogonal features of real languages. The self-referential application of object-oriented methodology to the development of object-based language paradigms is demonstrated.
Keywords
Computer Science
HAL (Le Centre pour la Communication Scientifique Directe)Smalltalk-80: The Language and its Implementation
3,896 Citations1983Adele Goldberg, D. Robson
This book is the first detailed account of the Smalltalk-80 system and is divided into four major parts: an overview of the concepts and syntax of the programming language, a specification of the system's functionality, and an example of the design and implementation of a moderate-size application.
Munich Personal RePEc Archive (Ludwig Maximilian University of Munich)Actors: A Model of Concurrent Computation in Distributed Systems
2,231 Citations1986Gul Agha
A foundational model of concurrency is developed and issues in the design of parallel systems and why the actor model is suitable for exploiting large-scale parallelism are addressed.
Communications of the ACMMonitors
1,498 Citations1974C. A. R. Hoare
This paper develops Brinch-Hansen's concept of a monitor as a method of structuring an operating system, introduces a form of synchronization, describes a possible method of implementation in terms of semaphores and gives a suitable proof rule.
ACM Computing SurveysConcurrency Control in Distributed Database Systems
1,165 Citations1981Philip A. Bernstein, Nathan Goodman
This paper describes a decomposition of the concurrency control problem into two major subproblems: read-write and write-write synchronization, and describes a series of synchromzation techniques for solving each subproblem and how to combine these techniques into algorithms for solving the entire conccurrency control problem.
Communications of the ACMAbstraction mechanisms in CLU
772 Citations1977Barbara Liskov, Alan Snyder +2 more
This paper provides an introduction to the abstraction mechanisms in CLU by means of programming examples, and it is shown how CLU programs may be written to use and implement abstractions.
Programming in Modula-2
609 Citations1985Niklaus Wirth
It is shown here how different types of computations, based on the number of parameters, can be implemented or modified according to the needs of a particular application.
ACM SIGPLAN NoticesUsing prototypical objects to implement shared behavior in object-oriented systems
542 Citations1986Henry Lieberman
Because any object can be used as a prototype, and any messages can be forwarded at any time, delegation is the more flexible and general of the two techniques.
Communications of the ACMDistributed processes
465 Citations1978Per Brinch Hansen
The paper gives several examples of distributed processes and shows that they include procedures, coroutines, classes, monitors, processes, semaphores, buffers, path expressions, and input/output as special cases.
ACM SIGPLAN NoticesAn introduction to Trellis/Owl
273 Citations1986Craig Schaffert, Topher Cooper +3 more
Encapsulation and inheritance in object-oriented programming languages
222 Citations1986Alan Snyder
This paper examines the relationship between inheritance and encapsulation and develops requirements for full support of encapsulation with inheritance.
Object-oriented programming with flavors
198 Citations1986David A. Moon
The philosophy and some of the major characteristics of Symbolics' newly redesigned object-oriented programming system, Flavors, are described and how the above goals are addressed are shown.
Delegation is inheritance
148 Citations1987Lynn Andrea Stein
This paper demonstrates that there is a “natural” model of inheritance which captures all of the properties of delegation and outlines a new framework which fully captures both delegation and inheritance.
Lecture notes in computer scienceThe Common Lisp Object System: An Overview
136 Citations1987Linda G. DeMichiel, Richard P. Gabriel
The Common Lisp Object System is an object-oriented system that is based on the concepts of generic functions, multiple inheritance, and method combination that has been proposed as a standard for ANSI Common Lisp and has been tentatively endorsed by X3J13.
DSpace@MIT (Massachusetts Institute of Technology)SPECIFICATION AND IMPLEMENTATION OF ATOMIC DATA TYPES
112 Citations1984William E. Weihl
This dissertation explores an approach in which atomicity is ensured by the data objects shared by concurrent activities; such objects are called Atomic objects, and data types whose objects are atomic are called atomic types.
ACM SIGPLAN NoticesAn exemplar based Smalltalk
85 Citations1986Wilf R. LaLonde, Dave A. Thomas +1 more
Theoretical Computer ScienceIntroduction to the theory of nested transactions
76 Citations1986Nancy Lynch, Michael Merritt
Topics in information systemsLanguage and Methodology for Object-Oriented Database Environments
64 Citations1988Stanley B. Zdonik, Peter Wegner
An object-oriented database language being implemented at Brown for use on workstations is described, and its use in defining an object- oriented programming environment is demonstrated.
NIL
63 Citations1983Robert E. Strom, Shaula Yemini
This paper presents features of the NIL programming language which support the construction of distributed software systems, a process model in which no pointers or shared data are visible, and compile-time typestate checking, guaranteeing module isolation and correct finalization of data.
Specification and implementation of resilient, atomic data types
46 Citations1983William E. Weihl, Barbara Liskov
This work defines what it means for abstract data types to be atomic and resilient, and discusses issues that arise in implementing such types, and describes a particular linguistic mechanism provided in the Argus programming language.
ACM SIGPLAN NoticesA comparison of the object-oriented and process paradigms
27 Citations1986Rob Strom
ACM SIGAda Ada LettersViewing Ada from a process model perspective
7 Citations1985Rob Strom, Shaula Yemini +1 more
This paper compares two programming language paradigms for large software systems and argues that the process model paradigm is simpler, has better support for modularity and programming-in the-large, and results in more reliable and maintainable programs.
A generalized object model
3 Citations1986Van Nguyen, Brent Hailpern
This work presents a new simple model of objects that allows multi-dimensional inheritance and behaves like communicating processes in Hoare’s CSP language, but with a different message-passing mechanism.