79 citations found. Retrieving documents...
S. E. Keene. Object-Oriented Programming in Common Lisp. Addison Wesley, 1989.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:

First 50 documents  Next 50

Position Paper - Adaptable And Adaptive   (Correct)

....to the natural evolution of a system from more disorganized states to more optimized ones, the object representation should also follow a natural evolutionary path. A lot of OODLs (object oriented dynamic languages) have been developed, for instance Smalltalk [GoRo83] SELF [UnSm87] CLOS [Keen89], and Dylan [Appl92] All these languages claim to support especially the development of adaptive software systems. Chameleon is an experimental OODL. Its outstanding aim is to support the evolutionary development of open yet secure object oriented systems by means of a simple object model as well ....

S.E.Keene; Object-Oriented Programming in Common Lisp; Addison-Wesley; 1989.


PCLOS: Stress Testing CLOS - Experiencing the Metaobject Protocol - Paepcke (1990)   (10 citations)  (Correct)

....focus of the more specific, detailed remainder of this paper. 2 Some CLOS Facts This paper cannot provide an in depth tutorial of CLOS. Reference [3] is the official reference for the CLOS programmer. It explains the concepts and contains manual pages for all the built in operations. Reference [4] is an excellent introduction with a good balance between formal and informal presentation. It also contains many useful examples. CLOS consists of the standard Common Lisp [5] with an object model added to it. We now outline the central concepts in just enough detail to prepare for a subsequent ....

Sonya E. Keene. Object-Oriented Programming in Common Lisp. Addison-Wesley Publishing Company, 1989.


Traits: Composable Units of Behaviour - Schärli, Ducasse, Nierstrasz, Black   (Correct)

....programmers have long realized that single inheritance is not expressive enough to factor out common features (i.e. instance variables and methods) shared by classes in a complex hierarchy. As a consequence, language designers have proposed various forms of multiple inheritance [7, 23, 29, 35, 41], as well as other mechanisms such as mixins [3, 10, 18, 27, 32] that allow classes to be composed incrementally from sets of features. Despite the passage of nearly twenty years, neither multiple inheritance nor mixins have achieved wide acceptance [44] Summarizing Alan Snyder s contribution to ....

Sonia E. Keene. Object-Oriented Programming in Common-Lisp. Addison Wesley, 1989.


Modules for Design Support - (ed.)   (Correct)

....scores are indicated and we see that there are still violated constraints. The next step would be performed as exemplified in figure c) 5. 5 Implementation The AAAO model is implemented in Common Lisp [ Steele, 1984 ] Steele:84) and its object oriented extension CLOS (Common Lisp Object System, Keene, 1989 ] Keene:89) The AAAO model is implemented in full detail for the adaptation of column positions on a floor to fit a certain use. The object oriented implementation, however, was designed to be extendable to other tasks in building design as well. All essential parts of the model are ....

S. Keene. Object-OrientedProgramming in Common Lisp. Addison-Wesley, 1989.


Traits: Composable Units of Behavior - Schärli, Ducasse, Nierstrasz, Black (2002)   (2 citations)  (Correct)

....programmers have long realized that single inheritance is not expressive enough to factor out common features (i.e. instance variables and methods) shared by classes in a complex hierarchy. As a consequence, language designers have proposed various forms of multiple inheritance [Mey88] Kee89] Str86] as well as other mechanisms, such as mixins [Moo86] BC90] FKF98] that allow classes to be composed incrementally from sets of features. Despite the passage of nearly twenty years, neither multiple inheritance nor mixins have achieved wide acceptance [Tai96] Summarizing Alan Snyder s ....

Sonia E. Keene. Object-Oriented Programming in Common-Lisp. Addison Wesley, 1989.


Uniform Representation of Basic Algebraic Structures.. - Limongelli, Malerba, .. (1996)   (Correct)

....in the matrix structure. After the specification of our structures is given (by following the formalism defined in [4] we present theironeimplementation in suitable classes. In this implementation the derivation of a structure from another is expressed by specialization inheritance. Clos [2] is the programming language used. It has been chosen for a number ofreasons: because of its object orientation# because it has been already used within a project, in whichwehave been involved, aiming to the development of a language for symbolic computation systems [3] and for our involvement in ....

Sonya E. Keene. Object OrientedProgramming in Common Lisp. Addison Wesley Publishing Company, 1989.


What's in a Name? - Ernst (2001)   (Correct)

....name. However, the e#ect of having multiple instance variables with the same 3 name is that the most specific one overrides the others; even though this can be used to simulate such features as class variables, it is also somewhat confusing and error prone. Finally, a defmethod form in a CLOS [6] program introduces a method implementation having a certain name and a certain argument list. This method will become one of the methods contained in some generic function of the same name having a congruent argument list (i.e. primarily, having the same number of required arguments) and ....

Sonya E. Keene. Object-Oriented Programming in Common Lisp. Addison-Wesley, Reading, MA, USA, 1989.


Evaluating Message Passing Control Techniques in Smalltalk - Ducasse (1999)   (5 citations)  (Correct)

....valueWithReceiver:arguments: defined on the class MethodWrapper. 5.2 Message Passing Control in Other Languages. CLOS is the object system integrated into Common Lisp. It is one of the few class based languages to offer the ability to define instance specific methods using the eql specializer[Kee89] Moreover CLOS is also one of the rare languages to provide a meta object protocol (MOP) in which message passing control is an entry point [KdRB91] In CLOS the message passing concept is replaced by the generic function 4 The CLOS MOP allows one to control all the aspects of the generic ....

S. E. Keene. Object-Oriented Programming in Common-Lisp. Addison-Wesley, 1989.


Separation of Concerns and Then What? - Ernst (2000)   (1 citation)  (Correct)

....C 3. When mixins [3, 2, 4, 9, 8] are supported, a mixin may be considered an aspect of the class to which it is applied 4. With multiple inheritance, a class C j may be considered as an aspect of a class C i in the construction of a new class C : C 1 : C k (as with CLOS style mixin classes [10]) 5. An AspectJ aspect may be considered as an aspect of the class it a ects (it may, e.g. add elds, methods, and statements within methods to its target class) 6. A module system (such as the one in gbeta) can support the addition of local classes, elds, and methods to classes, cases to ....

Sonya E. Keene. Object-Oriented Programming in Common Lisp. Addison-Wesley, Reading, MA, USA, 1989.


Dynamic Inheritance In A Statically Typed Language - Ernst (1999)   (Correct)

....with the same name, inherited from two or more superclasses. Which one of those attributes should be used for a given application of the common name One way to automatically resolve ambiguities is to linearize the inheritance graph. This approach was taken in several languages including CLOS [18] and Dylan [33] An extra bene t of linearization is that not only name lookup but also method combination has a natural de nition when the list of superclasses has been established. In CLOS, e.g. method combination is supported using before methods, after methods, and call next method. The ....

....All these systems are very exible. The exibility goes along with a very rich universe of potential program executions, and this makes it dicult to prove that any speci c properties hold about individual program elements in other words, they are not designed for static type checking. The CLOS [18] convention of using some classes for mixin inheritance has been developed [5, 11, 34] into a separate concept of mixin based inheritance. A mixin is a class modifying device, supporting inheritance directly as an incremental modi cation that may be applied to several di erent classes. In [34, ....

Keene, Sonya E. 1989. Object-Oriented Programming in Common Lisp. Addison -Wesley, Reading, MA, USA.


Propagating Class and Method Combination - Ernst (1999)   (7 citations)  (Correct)

....particular language, but that is only because so few object oriented languages offer general block structure and virtual classes. With the introduction of inner classes in Java and the possible addition of virtual types [24] or a similar mechanism, the same techniques would apply here. Since CLOS [12] programmers introduced mixin classes as a particular programming style in context of linearization based multiple inheritance, a related but separate concept of mixins and mixin based inheritance has emerged [2, 3, 23, 8] Inheritance allows for the creation of one new class, based on zero or ....

....as mentioned in Sect. 4, the fundamental mechanisms of gbeta the new semantics of virtuals and the support for class combination are so different that a complete reimplementation was required. To our knowledge there are no existing systems which support a mechanism like our propagation. CLOS [12] was an important source of inspiration, and gbeta does not have an equivalent of the CLOS meta object protocol; it is probably necessary for static type checking to lay down a firm foundation for the language and not let everything be user definable. Thus, in addition to the propagation ....

Sonya E. Keene. Object-Oriented Programming in Common Lisp. Addison-Wesley, Reading, MA, USA, 1989.


Reasoning About Polymorphic Behavior - Soundarajan, Fridella (1998)   (1 citation)  (Correct)

....need considerable modification. 12 We should also mention the work of Lamping and Abadi [8] in which they formalize polymorphism in a very general manner allowing method selection to depend on a variety of criteria such as on the types of all the operands (multi methods as in Cecil [3] or CLOS [7]) or even real time considerations (as in DROL [15] But their focus is on formalizing how the method is chosen (by the run time system) rather than on reasoning about behaviors. Nevertheless it would be interesting to see if some of their ideas can be used as a generalization of our ObIds, ....

S. E. Keene. Object-Oriented Programming in Common Lisp. Addison-Wesley, 1989.


Modular Formal Frameworks for Module Systems - Ancona (1998)   (5 citations)  (Correct)

No context found.

S. E. Keene. Object-Oriented Programming in Common Lisp. Addison Wesley, 1989.


MultiPerspectives: Object Evolution and Schema Modification.. - Odberg (1995)   (11 citations)  (Correct)

No context found.

Sonya E. Keene. Object-Oriented Programming in COMMON LISP. A Programmers Guide to CLOS. Addison-Wesley, 1989.


Amalgams: Names and Name Capture in a Declarative Framework - Michel, Giavitto (1998)   (Correct)

No context found.

Keene, S. E. Object-Oriented Programming in Common Lisp. Addison Wesley, Reading, Mass., 1989.


Modularity Meets Inheritance - Gilad Bracha Gary (1991)   (66 citations)  (Correct)

No context found.

Keene, S. E. Object-OrientedProgramming in Common Lisp. Addison-Wesley, 1989.


The Design of Object-Oriented - Meta-Architectures For Programming (1994)   (Correct)

No context found.

Keene, S. E., (1989), Object-OrientedProgramming in Common Lisp. Reading, MA: AddisonWesley.


Object-Oriented Programming in Scheme with First-Class.. - Banavar, Lindstrom (1995)   (Correct)

No context found.

Sonya E. Keene. Object-Oriented Programming in Common Lisp. Addison-Wesley, Reading, MA, 1989.


The Design of Object-Oriented - Meta-Architectures For Programming (1994)   (Correct)

No context found.

Keene, S. E., (1989), Object-Oriented Programming in Common Lisp. Reading, MA: AddisonWesley.


Matching Scores and Performances - Hank Heijink Graduate   (Correct)

No context found.

Sonya E. Keene, Object-Oriented Programming in Common LISP, Addison-Wesley (1989).


Experiences in Database System Implementation Using a Persistent.. - Hanson   (Correct)

No context found.

Sonya E. Keene, Object-Oriented Programming in Common Lisp, Addison-Wesley, 1989.


Making C++ Objects Persistent: the Hidden Pointers - Biliris, Dar, Gehani (1993)   (1 citation)  (Correct)

No context found.

S. E. Keene, Object-Oriented Programming in Common Lisp, Addison-Wesley, 1989.


A Scheme for Little Languages in Interactive Graphics - Beckman (1991)   (11 citations)  (Correct)

No context found.

S.E. Keene, Object-Oriented Programming in Common Lisp, A Programmer's Guide to CLOS, Addison-Wesley, Reading, MA, 1988.


Implementing OKBC Knowledge Model Using Object Relational.. - Luo, Chaudhri   (Correct)

No context found.

Sonya E. Keene. Object-Oriented Programming in Common Lisp, Addison-Wesley Publishing Company, 1988.


Design and Implementation of an Enhanced Object-Oriented Model for .. - Miale (1993)   (Correct)

No context found.

Sonya E. Keene. Object-Oriented Programming in Common Lisp. Addison-Wesley, Reading, Mass., 1989. 43

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