D. Bobrow, L. DeMichiel, R. Gabriel, S. Keene, G. Kiczales, and D. Moon. Common lisp object system specification: X3j13 document 88-002r. SIGPLAN Notices, Vol. 23,, 1988. Special Issue.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....at the workshop Eiffel in Schule und Hochschule in Darmstadt, May 1995. y Department of Mathematics and Computer Science, Fredrik Bajers Vej 7E, 9220 Aalborg , Denmark. Internet: normark iesd.auc.dk. 1 Semester # Basis 1 Basis 2 Math 1 Math 2 El. Eng. 1 El. Eng. 2 Computer Science 1 (CS1) 1 2 3 4 5 Computer Science 2 (CS2) 6 Computer Science 6 (CS6) 10 . Figure 1: The structure of the first five semesters. methodologically to carry out problem oriented projects. The students who follow the two Electrical Engineering semesters in addition learn to program in C. ....

....language, and our specific experience with Eiffel 3.1. 3.1 Why choosing Eiffel It is a difficult and serious enterprise to choose a programming language for a computer science semester. In 1991 we considered the following languages for CS1: Simula [ 3 ] Smalltalk [ 4 ] Beta [ 7 ] CLOS [ 1 ] Eiffel [ 9 ] and C [ 15 ] The following criteria were used in the selection process: 1. The language must reflect a trend in modern programming language design. 2. The language must not be homegrown nor exotic . 3. The language must be statically typed. 4. The language must ....

[Article contains additional citation context not shown here]

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonay E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp object system specification X3J13 document 88-002R. Sigplan Notices, 23(Special Issue), September 1988.

....rule6, rule5, rule4, rule3, rule2, rule1. These rules are ordered lexicographically, based on topo logical sorts of PascalStandard and its super schemes 4 , and Program and its supertypes. The inspiration for this ordering strategy comes from the object oriented programming language CLOS [2]. As can be seen, we give first priority to entity types, and second priority to the interaction schemes. Thus, when finding the mutual order of two rules r1 and r2, we only take the association to interaction schemes into account if the rules are associated with the same entity type. In the ....

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonay E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp object system specification X3J13 document 88-002R. Sigplan Notices, 23(Special Issue), September 1988.

....L2 gives the center of the resulting circle. The actual data structures behind the trace is a tree implemented in the Common Lisp 4 The central line of a line segment L is a line segment of the same length as L, perpendicular on L, which intersects L in its midpoint. 15 Object System (CLOS) 1 ] A sketch of such a tree is shown in figure 7. 5 The tree is akin to an abstract syntax tree. In the current, early prototype, the tree is built via a simple custom made structure editor. The structure editor works via a number of specialized commands which augment, change and prune the tree ....

....and two other points p1 and p2. Create Line1 through receiver point and p1. Create the central line of Line1 Create Line1 through receiver point and p2. Create the central line of Line2. If not parallel (central line1, central line2) then create intersection point IP between central line 1 and central line 2. Find distance D between point and IP. Draw the circle with center IP and radius D. Create Central line Create Central Line1 Distance . Par. Create circle Figure 13: An interaction diagram for the circle construction problem. One of the main difficulties is ....

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonay E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp object system specification X3J13 document 88-002R. Sigplan Notices, 23(Special Issue), September 1988.

....ActiveValue. Similarly, execution time binding of open points is achieved because of the properties of Loops host environment, which is Interlisp. There is no provision for any particular documentation of active values in Loops. 4. 5 Generic Functions in CLOS The Common Lisp Object System (CLOS) [6] is open in the same way as Smalltalk, but in addition and as an alternative the method combination facility (explained below) provides CLOS with yet another kind of open points. In CLOS, a generic function can be a combination of several methods. Using standard method combination, a generic ....

....value of the first of these (the value of P 1 applied on the 4 In Lisps in which procedures are not first class objects, one may prefer to use procedure names in hook attach and hook detach. 5 The hook combinator mechanism is inspired by the simple built in method combination mechanism in CLOS [6]. 5 ELABORATION OF HOOKS IN A LISP ENVIRONMENT 16 argument list) The last combinator also executes the procedure in attachment order, but it returns the value of the last of these applications. The fist non nil combinator similarly executes the procedure in attachment order, but only until one ....

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonay E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp object system specification X3J13 document 88-002R. Sigplan Notices, 23(Special Issue), September 1988.

....collected. In the same way, the ET rules which belong to each of the super schemes of I is consulted and collected. The immediate super schemes of I are examined in an order from left to right, as found in the definition of I. Readers that have knowledge of the Common Lisp Object System (CLOS) [1] will recognize that we are inspired by the CLOS technique for resolution of ambiguities implied by multiple inheritance. Finally, the whole collection process is repeated on each entity type in the chain of super entities of ET. Relative to figure 4.2 the sequence of rules 5, 4, 3, 2, and 1 ....

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonay E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp object system specification X3J13 document 88-002R. Sigplan Notices, 23(Special Issue), September 1988.

....the creation and deletion of these during the program execution. Classes versus instances of classes may serve as an example of the difference between the elements of the two models. The distinction between static and dynamic models, considered as abstractions, will be discussed further in section 2 below. In this paper we will restrict the discussion of dynamic models to object oriented design situations. In general, a design is a plan for construction. An object oriented design is a design in which classes and methods play a key role in the static design models, and in which objects and ....

....it may be a relevant design decision to state if and when an object becomes irrelevant. 3 Although it is conceived that a message activates a method from the class of the receiver object, the method concept is weak in our dynamic model. It is known to be the case that the message passings in item 2 from above are located in one single method in the class (say C) of the receiver object R. However, the same message to another object of the class C, or the same message to R with other actual parameters, may cause another sequence of messages from R (for instance because of selections with ....

[Article contains additional citation context not shown here]

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonay E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp object system specification X3J13 document 88-002R. Sigplan Notices, 23(Special Issue), September 1988.

....object scopes its attributes and methods, incremental composition will not result in naming issues. 4. 3 Meta level approaches A metaobject protocol (MOP) is an interface that allows a programmer to customize properties of the programming language, such as adding persistence and concurrency [3, 12]. A reflective programming language is one which supports such customizations, allowing the program to reason about its own execution state and alter behavior accordingly [23] The context relation and context objects can be implemented using reflection. Open Implementation (OI) principles ....

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonya E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp object system specification: X3J13 document 88-002R. volume 23. ACM Press, September 1988. Special Issue of SIGPLAN Notices.

....an intriguing new approach to the foundations of object oriented programming. Taking overloading and subtyping as basic, instead of encapsulation and subtyping, they develop an underlying calculus that promises to model some features notably the generic functions of languages such as CLOS [3] that fall completely outside the scope of previous theories, including ours. However, their account does not yet include some of the characteristic features of objectoriented programming, encapsulation in particular, that have motivated our constructions. 7 Future Work The extension of ....

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonya E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp Object System specification X3J13 document 88-002R. SIGPLAN Notices, 23, 1988.

No context found.

D. Bobrow, L. DeMichiel, R. Gabriel, S. Keene, G. Kiczales, and D. Moon. Common lisp object system specification: X3j13 document 88-002r. SIGPLAN Notices, Vol. 23,, 1988. Special Issue.

No context found.

D. G. Bobrow, L. G. DeMichiel, R. P. Gabriel, S. E. Keene, G. Kiczales, and D. A. Moon. Common LISP object system specification X3J13 document 88-002R. ACM SIGPLAN Notices, 23, 1988. Special Issue, September 1988.

No context found.

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonya E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp object system specification: X3J13 document 88--002R. ACM SIGPLAN Notices, 23(Special Issue), September 1988.

No context found.

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonya E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp object system specification: X3J13 document 88-002R. volume 23. ACM Press, September 1988. Special Issue of SIGPLAN Notices.

No context found.

Daniel G. Bobrow, Linda G. DeMichiel, Richard P. Gabriel, Sonya E. Keene, Gregor Kiczales, and David A. Moon. Common Lisp Object System specification X3J13 document 88-002R. SIGPLAN Notices, 23, 1988.

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