Adele Goldberg and D. Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....to it. A Linda layer can act as glue between languages of di#erent paradigms. Let us now look at more substantive solutions. Within the imperative paradigm, there have been several e#orts to add the abilities of functional programming. Smalltalk has blocks , which are lexically scoped closures [38]. Java has inner classes, which (with minor limitations) are lexically scoped closures. Java supports the final annotation, which allows programming with stateless objects. Using inner classes and final allows to do functional programming in Java. However, this technique is verbose and its use is ....

Adele Goldberg and David Robson. Smalltalk-80: The language and its implementation. Addison-Wesley, 1983.

....to the optimisation phase, to take advantage of these existing tools. 6. 2 Shift to Object Orientation Object oriented programming, while invented in the 60 s with Simula 67 [14] became popular in the late 80 s and early 90 s with the availability of programming languages such as Smalltalk [27], C [61] and Java [28] Some programmers adopted object oriented ideas while still working with non objectoriented languages. In fact, research continues on how to express object oriented features in procedural languages such as C [17] While implementations of these features in C may not look ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and Its Implementation. Addison-Wesley Longman, Inc., 1983.

....the flavor of a preprocessor or are integrated with the compiler of the language. An example of such a system is the template system in C [Str97] 2. Run time Metaprogramming: The meta program is employed at run time and are usually integrated in the programming language, such as in Smalltalk [GR83] Declarative metaprogramming combines a declarative language used at the meta level together with a certain base language (e.g. an object oriented language) 5.3 Logic Metaprogramming Logic metaprogramming is a particular instance of declarative metaprogramming. The declarative language that is ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and Its Implementation. Addison-Wesley, 1983.

....systems are able to benefit from object orientation to maximize code reuse and provide polymorphism. Furthermore, it is not clear how to add new features such as delegation in such systems. Other systems are object oriented or object based, including Chorus [Mar88] Apertos [Yok92] and Smalltalk [GR83]. However, none of these have addressed means of providing authentication and delegation. Background In this chapter we introduce terms and concepts used throughout the remainder of the thesis. We present the advantages of an object oriented environment; this may be safely skipped by a reader ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, Reading, Massachusetts, 1983.

....[Weg90] Objects are abstract entities that describe computational components through their behaviour and state. They constitute the basic building blocks of programs and systems. Within this paradigm, not only have several languages emerged and stabilised like Simula [DN67, ND81] and Smalltalk [GR83] but being C [Str91] and Java [GJS96] the more widely used among them but also a very large body of research has been formed. Nowadays, object oriented notions, as abstraction, encapsulation, or inheritance, play a central role in software and hardware development. Basic research has made ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

....and change the entry for the superclass appropriately. This copy could be avoided by modifying the virtual machine to compute super when needed. In Smalltalk, classes are first class objects; every class is instance of a metaclass that defines the shape and the behaviour of its singleton instance [19]. In our implementation, we support this concept by introducing the notion of a metatrait; a metatrait can be associated with every trait. When a trait is used in a class, the associated metatrait (if there is one) is automatically used in the metaclass. Note that a trait without a metatrait can ....

Adele Goldberg and David Robson. Smalltalk 80: the Language and its Implementation. Addison Wesley, Reading, Mass., May 1983.

....of significant size. We chose the Smalltalk collections classes as the target for such an evaluation. 5. THE SMALLTALK COLLECTION The collection classes are a loosely defined group of general purpose subclasses of Collection and Stream. The group of classes that appears in the Blue Book [13] contains 17 sub classes of collection and 9 sub classes of Stream, for a total of 28 classes, and had already been redesigned several times before the Smalltalk 80 system was released. This group of classes is often considered to be a paradigmatic example of object oriented design. In Squeak, ....

Adele Goldberg and David Robson. Smalltalk 80: the Language and its Implementation. Addison Wesley, Reading, Mass., May 1983.

....inheritance, and with mixins. We have also reported on the use of an experimental implementation to refactor a part of the Smalltalk collections hierarchy [BSD02] The semantics of single inheritance is well understood and it is described by several operational and denotational formalizations [GR83,CP89]. For conciseness, we do not repeat any details of these formalizations. Instead we focus on two contributions. First, we define traits and the various operators that can be used to combine traits into compound traits, and ultimately into classes. Second, we make precise the internal dependencies ....

Adele Goldberg and David Robson. Smalltalk 80: the Language and its Implementation. Addison Wesley, Reading, Mass., May 1983.

....software development. However, this flexibility comes at a price: due to their weak types, runtime type errors can occur. Class based programming o#ers the possibility of creating more robust programs, owed in part to the static type systems of these languages. A notable exception is Smalltalk[10] which is class based but weakly typed. Classes and types in object oriented programming languages have overlapping, but not identical roles: Classes organize the code, and describe the behaviour of objects, whereas types describe the interface of objects. Although it has been successfully argued ....

....guided by the formal definitions and proof of soundness rather than aim to have a large number of features. BeCecil[4] is a formalization of a variant of Cecil, however it does not have incremental typing and no soundness proof is given. Strongtalk[8, 2] is an incremental typechecker for SmallTalk[10]. It uses structural rather than named types. It supports parameterized types and classes. However, the approach is class based rather than starting object based and using types to obtain a class based program. 7 Conclusions and Future Work The style of programming we aim to support with this ....

Adele Goldberg and David Robson. SmallTalk-80 The Language and its Implementation. ADDWES, 1983.

....to a large framework. We chose the Smalltalk Collections Hierarchy for this experiment. 5 The Smalltalk Collection Hierarchy The collection hierarchy is a loosely defined group of general purpose subclasses of Collection and Stream. The version of the hierarchy that appears in the Blue Book [GR83] contains 17 sub classes of collection and 9 sub classes of Stream, for a total of 28 classes, and had already been redesigned several times before the Smalltalk 80 system was released. This group of classes is often considered to be a paradigmatic example of object oriented design. In Squeak, ....

Adele Goldberg and David Robson. Smalltalk 80: the Language and its Implementation. Addison Wesley, Reading, Mass., May 1983.

....and change the entry for the superclass appropriately. Copying could be avoided by modifying the virtual machine to compute super when needed. In Smalltalk, classes are first class objects; every class is instance of a metaclass that defines the shape and the behaviour of its singleton instance [GR83] In our implementation, we support this concept by introducing the notion of a metatrait; a metatrait can be associated with every trait. When a trait is used in a class, the associated metatrait (if there is one) is automatically used in the metaclass. Note that a trait without a metatrait can ....

Adele Goldberg and David Robson. Smalltalk 80: the Language and its Implementation. Addison Wesley, Reading, Mass., May 1983.

....user. The above mentioned properties are typical for GUI interfaces. An application may, for example, spawn multiple windows and the user may be able to point and click on objects of interest. An early example of a windowing system is the Smalltalk graphical, interactive programming environment [41]. Smalltalk is known as the purest object oriented programming language. For describing the design of the visualization the ModelView Controller (MVC) paradigm is borrowed from the Smalltalk terminology. Figure 31 illustrates the concept. The model is used to represent the data or knowledge ....

Adele Goldberg and David Robson. Smalltalk-80 --- The Language and its Implementation. Addison-Wesley Publishing Company, 1983.

....JUDO [CLS00] and the Open Runtime Platform [CLS02] and IBM s Jalapeno [AAB 00] use dynamic compilation techniques to produce good quality native code. These techniques have been derived over time from virtual machine technology used to implement object oriented languages such as Smalltalk [GR83] DS84] and Self [US87] Hol94] Self was the inspiration for the original Java HotSpot virtual machine. The architecture of optimizing virtual machines is based on the premise that most programs spend 90 of the time in 10 of the code therefore, the VM only optimizes that 10 of the code ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and Its Implementation. Addison-Wesley, Reading, MA, 1983.

....job. Most programming languages support only the metaphor of objects for using state. The simplest languages give the programmer state variables, simple objects that can be read and written. More advanced languages provide abstraction mechanisms that support the construction of abstract objects [GR83, LAB 81, Moo86, Agh86] which support more complex operations. The object metaphor is that objects serve as containers for state. Each container divides the system into two parts, consisting of the users of the container, and the keepers of the container. If the container is a state variable, ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

....(e.g. electronic white boards) involve only humans and therefore focus on providing a wide range of mechanisms specific to human computer interaction. 2.3. 4 Workflow and Computer Simulation Computer simulation uses software models of real world concepts to model situations that change over time [47]. Simulators gather statistics about the models they simulate. Workflow resembles computer simulation in that the process descriptions workflow systems execute are in fact software models representing real processes. At run time, the workflow management system records data about how the process ....

Adele Goldberg and David Robson. Smalltalk--80: The Language and its Implementation. AddisonWesley, Reading, Massachusetts, 1983.

....their enclosing de nitions. In fact, the rst object oriented language, Simula [3] did support nested class declarations. Although most succeeding object oriented languages left them out, a few object oriented languages follow Simula and support various kinds of nesting. For example, Smalltalk [9] has special syntax for block objects, similar to anonymous functions. Beta [17] provides patterns, unifying classes and functions, that can be nested arbitrarily. More recently, inner classes have been popularized by their inclusion in Java 1.1 [10, 14] Inner classes are useful when an object ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and Its Implementation. Addison-Wesley, Reading, MA, 1983.

....space consumption of customization to within 34 or less of a completely non customizing system. Thus, even in dynamically compiled systems customization and efficient memory usage need not be mutually exclusive. 1. Introduction Pure object oriented languages such as Self [US87] or Smalltalk [GR83] are difficult to implement because of the high frequency of virtual method calls [DS84] CUL89] Much previous work has attempted to overcome this performance problem with a suite of optimization techniques aimed at reducing the cost of dynamic dispatch: inlining [CU93] customization ( CU89] ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and Its Implementation. AddisonWesley, Reading, MA, 1983.

....Results are expressed relative to the original JDK 1.1.4 interpreter which would score 1.0 in each category. This provides a mechanism for introducing class specific processing into standard method invocations. It is therefore similar to the meta class facilities provided in Smalltalk [GR83] or in some extended dialects of C [MMAY95] However, unlike traditional metaclass designs, the dispatcher scheme provides clearer separation between the implementation (and perhaps the implementor) of a class and meta class. For example, figure 8 shows how dispatchers may be used to ....

....when generating optimized code. The issue of how to control compile induced pauses in execution is not addressed. This is perhaps a consequence of the necessity of run time compilation for acceptable performance (many of the initial interpreted implementations of the Smalltalk 80 virtual machine [GR83] were found to be intolerably slow [Kra84] Self [CUL89] is a dynamically typed pure prototype based object oriented language. It encourages a style of programming in which message send operations are extremely frequent and, as with Smalltalk, it is designed to provide an exploratory ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

....The mapping from package names to dispatchers is maintained by static methods of dispatcher.DispatcherRegistry. This provides a mechanism for introducing class specific processing into standard invocations. It is therefore similar to the meta class facilities provided in Smalltalk systems [GR83] or in some extended dialects of C [MMAY95] However, unlike traditional meta class designs, the dispatcher scheme provides clearer separation between the implementation (and perhaps the implementor) of a class and meta class. For example, Figure 6 shows how dispatchers may be used to ....

....when generating optimized code. The issue of how to control compile induced pauses in execution is not addressed. This is perhaps a consequence of the necessity of run time compilation for acceptable performance (many of the initial interpreted implementations of the Smalltalk 80 virtual machine [GR83] were found to be intolerably slow [Kra84] Self [CUL89] is a dynamically typed pure prototype based object oriented language. It encourages a style of programming in which message send operations are extremely frequent and, as with Smalltalk, it is designed to provide an exploratory ....

[Article contains additional citation context not shown here]

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

....that experience gained during implementation phases will feed back and help to refine designs. 4 Related work It is not new to use a virtual machine as the target for a high level language. Before Java, perhaps the most widely known example for an object oriented language was Smalltalk 80 [GR83, Kra84] As with Java, Smalltalk aims to allow portability of applications between implementations. It provides the programmer with more access to details of the virtual machine for example stack frames are exposed as mutable objects. It is intended to be an exploratory programming ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

....terms in this dissertation have come to be used elsewhere with a variety of meanings. This section clarifies how they will be used here. 5 Virtual machines The term virtual machine is used in this dissertation to refer to systems such as the Java Virtual Machine [Lindholm97] and Smalltalk vm [Goldberg83] typified by the use of a non native instruction set, a substantial set of standard library functions and an implementation that exposes only high level interfaces to the resources of the underlying system. Such systems effectively provide the complete set of services that an application ....

....calls. A special call standard procedure operation is provided to invoke library facilities such as file access or trigonometric computation. Smalltalk 80 2.1. 3 Smalltalk was conceived towards the end of the 1970s as a new way that people might effectively and joyfully use computing power [Goldberg83] In Smalltalk 80 this is realized in a pure class based object oriented programming language [Krasner84] 1 . Unlike impure object oriented languages (such as C [Stroustrup97] Modula3 [Nelson, editor91] or Java [Gosling97a] all computation is notionally performed by dynamic method ....

[Article contains additional citation context not shown here]

Adele Goldberg and David Robson. Smalltalk-80: the Language and its Implementation. Addison-Wesley, 1983. (pp 6, 11, 14)

....implementations and better programming practice. 5.3 Further Literature There is by now such a vast amount of related work that we can hardly do more than cite examples almost at random, including the following: 1. Implementations of inheritance in Simula [12] as further developed in Smalltalk [37] and other object oriented languages. 2. Overloading and subtypes in Ada [13] 3. The theory of (higher order) polymorphism as developed in [58] 68] 8] and [55] among many others. 4. There has been recent work on adding subtypes to higher order calculi [7, 2] 37 5. Work on classified ....

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

....result of Domani et al. are incomparable with those of Bacon et al. 3] since Bacon et al. report the exact pause times, measured by the Jalapeno JVM. 1. 8 Related work The traditional method of reference counting, was rst developed for Lisp by Collins [10] It was later used in Small talk 80 [22], the AWK [1] and Perl [39] programs. Improvements to the naive algorithm were suggested in several subsequent papers. Weizman [40] studied ameliorating the delay introduced by recursive deletion. Deutsch and Bobrow [14] eliminated the need for a write barrier on local references (in stack and ....

Adele Goldberg and D. Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

....it in a combined modeling and runtime environment. The centerpiece of this system is a virtual machine that directly interprets UML models. A UML virtual machine, like any virtual machine, is an abstract computing machine. It provides an instruction set and a memory model for representing objects [13, 6]. As the instruction set of the virtual machine, we use UML itself. UML provides several behavior modeling capabilities that can be used to describe the behavior of a model (including itself) 2 Models are persistently represented using XMI, the OMG standard for representing UML models using ....

....for integrating independently developed domain models in UML based modeling. 7 RELATED WORK We discuss related work on virtual machines, metalevel architectures, model driven software systems and UML based software development tools. Virtual machines for programming languages like Smalltalk [6], Self [31, 9] and Java [1, 13] have both inspired this work as a metaphor and provided solid implementation advice. Like Smalltalk and Self, and unlike Java, we fully represent the modeling language using the system s own capabilities. The architecture of the virtual machine, however, probably ....

Adele Goldberg and David Robson. Smalltalk: The Language and Its Implementation. Addison-Wesley, 1983.

....of functional languages is too voluminous to be included. The Scheme language is described in [30] the ML language in [67] and the Miranda language in [107] Simple polymorphic type systems are introduced in [47, 66] Slide 12,18 Simula and Beta are described in [36, 37, 56, 62] Smalltalk in [42, 43]; CLOS in [53] Self in [108, 29, 26] C in [98, 97, 100] and Eiffel in [64, 65, 39] Slide 21 26 The formalization of coercion functions is found in [89, 90] Slide 27 The use of coercion theory for phrase types is developed in [91, 75, 92] and for implicit scalings in [103] Slide 28 38 ....

Adele Goldberg and David Robson. Smalltalk-80---The Language and its Implementation. Addison-Wesley, 1983.

No context found.

Adele Goldberg and D. Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, Menlo Park, California, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The language and its Implementation. Addison Wesley, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addision-Wesley, Reading, MA, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, Reading, MA, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: the language and its implementation. Addison-Wesley Longman Publishing Co., Inc., 1983.

No context found.

Adele Goldberg, and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, Reading, 1985.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and Its Implementation. Addison-Wesley, Reading, MA, 1983.

No context found.

Adele Goldberg, David Robson. Smalltalk-80: the Language and its Implementation. Addison-Wesley, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and Its Implementation. Addison-Wesley, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. AddisonWesley, 1983.

No context found.

Adele Goldberg and D. Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and Its Implementation. Addison-Wesley, Reading, Massachusetts, 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley Press, Reading, Mass., 1983.

No context found.

Adele Goldberg and David Robson. Smalltalk-80: The Language and Its Implementation. Addison-Wesley, Reading, MA, 1983.

No context found.

Adele Goldberg and Dave Robson. Smalltalk-80: The Language and its Implementation. Addison Wesley, 1983. 714 pp.

No context found.

Adele Goldberg and D. Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.

No context found.

Adele Goldberg and David Robson, Smalltalk-80: The Language and its Implementation, AddisonWesley, Reading, Massachusetts, 1983.

No context found.

Adele Goldberg and David Robson, Smalltalk-80: The Language and its Implementation. AddisonWesley, Reading, Massachusetts, 1983.

No context found.

Adele Goldberg and David Robson, Smalltalk-80: The Language and its Implementation, AddisonWesley, Reading, Mass. 1983.

No context found.

Adele Goldberg and David Robson, Smalltalk-80: The Language and Its Implementation, Addison-Wesley, Reading, MA, 1983.

No context found.

Adele Goldberg and David Robson, Smalltalk-80 -- The Language and its Implementation, Addison-Wesley, New York, 1983.

No context found.

- Adele J. Goldberg and David Robson, SmallTalk-80: The Language and Its Implementation, Addison-Wesley, 1983.

No context found.

Colberg, Adele and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, Reading, Ma, 1983.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC