Gregor Kiczales, Jim des Rivieres and Daniel G. Bobrow, The Art of the Metaobject Protocol, MIT Press (Ed.), 1991.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....of the form type name = type definition We can also define type operators (like ) using the following syntax type type operator = Fun(type parameter) type definition as in the expressions 6. Implementation of Generic Synchronization Policies type Pair = Fun(X) X,X] val x : Pair Int = [2,3] 3.2 Processes A process can be either a sender process or a receiver process. The syntax of a sender process is channel name value whereas a receiver process is channel name pattern process or channel name pattern process A sender process can only communicate with another receiver ....

....The run directive allows a process expression to be put in parallel with the rest of the program, so that our example could also have been written as new x run x 3 run (x y printi y) As we have seen in 3. 1, tuples of values can be used to transmit more than one value at a time new x run x [3,4] (x [y,z] printi y printi z) In this case the values 3 and 4 will be displayed (but in an unspecified order) It is important to note that the parallel composition of two processes (the operator) is itself a process. Consider now the following program: new x run x 3 x 4 (x y ....

[Article contains additional citation context not shown here]

Gregor Kiczales, Jim des Rivieres and Daniel G. Bobrow, The Art of the Metaobject Protocol, MIT Press (Ed.), 1991.

....is opened up (allowing client programmers to extend it as they see fit) thus departing from the traditional black box approach to modular software. In other words, we allow limited visibility inside the library. This approach is similar to the metaobject implementation techniques of CLOS [5], where the objects of the implementation (also called metaobjects) allow the behavior of the system to be controlled and modified. If we think of traditional software reuse (e.g. 2] this clearly goes beyond the simple function library approach. The classes in our library have various roles ....

Gregor Kiczales, Jim des Rivieres and Daniel G. Bobrow, The Art of the Metaobject Protocol, MIT Press, Cambridge (Mass.), 1991.

....inverse slots) Otherwise PORK behaves exactly like standard CLOS, thus allowing PORK and CLOS code to be freely mixed. PORK also has a metaobject protocol to allow the system to be extended (for an introduction of metaobject programming we recommend the book The Art of the Metaobject Protocol [6] which explains the philosophy of metaobject protocols as well as documents the proposed standard MOP for CLOS) PORK, as an extension of CLOS, adheres to the class instance paradigm. Other frame systems, where the distinction between class instance and prototype instance approaches is blurred ....

....modified as well. Use the :fragile option with extreme care. It should be mentioned that class allocation of relation slots is not allowed in PORK (specifying the value :class for :allocation) Ordinary CLOS slots can use class allocation. 2. 7 Extending the System Terminology note: According to [6], metaobjects (i.e. classes, generic functions, methods etc. can be divided into three categories: those defined in CLOS MOP are called specified, those defined by an implementation (of CLOS) are called implementation specific, and those defined by a portable program are called portable. In ....

[Article contains additional citation context not shown here]

Gregor Kiczales, Jim des Rivi`eres and Daniel G. Bobrow, 1991. The Art of the Metaobject Protocol, Cambridge (MA), MIT Press.

No context found.

Gregor Kiczales, Jim des Rivi`eres and Daniel G. Bobrow. The Art of the MetaObject Protocol. The MIT Press. Cambridge, Massachusetts, 1991.

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