Why Smalltalk?
Saved in:
| Title: | Why Smalltalk? |
|---|---|
| Authors: | Goldberg, Adele1 |
| Source: | Communications of the ACM. Oct95, Vol. 38 Issue 10, p105-107. 3p. |
| Subjects: | Smalltalk (Computer program language), Programming languages, Computer systems, Systems design, Computer simulation, Games |
| Abstract: | Smalltalk is a single paradigm language with very simple semantics and syntax for specifying elements of a system and for describing system dynamics. When the language is used to describe an application system, the developer extends Smalltalk, creating a domain-specific language by adding a new vocabulary of language elements while maintaining the same semantics and syntax. System parts in Smalltalk are descriptions known as objects. An object can delegate responsibility to other objects to provide expected services (composition), or to inherit the capacity to carry out services from other objects that can then be extended. Smalltalk's heritage is simulation. The Smalltalk language design was motivated by the desire to enable users to easily describe their real-world models (business processes, games, educational interactions) as computer models, and to be able to experiment. The focus on simulation created a design requirement that the user be able to rapidly change the underlying conceptual model, not just the data used by a fixed program. |
| Database: | Engineering Source |
| Abstract: | Smalltalk is a single paradigm language with very simple semantics and syntax for specifying elements of a system and for describing system dynamics. When the language is used to describe an application system, the developer extends Smalltalk, creating a domain-specific language by adding a new vocabulary of language elements while maintaining the same semantics and syntax. System parts in Smalltalk are descriptions known as objects. An object can delegate responsibility to other objects to provide expected services (composition), or to inherit the capacity to carry out services from other objects that can then be extended. Smalltalk's heritage is simulation. The Smalltalk language design was motivated by the desire to enable users to easily describe their real-world models (business processes, games, educational interactions) as computer models, and to be able to experiment. The focus on simulation created a design requirement that the user be able to rapidly change the underlying conceptual model, not just the data used by a fixed program. |
|---|---|
| ISSN: | 00010782 |
| DOI: | 10.1145/226239.226260 |
