A. Farkas and A. Dearle. Octopus: A reflective language mechanism for object manipulation. In C. Beeri, A. Ohori, and D.E. Shasha, editors, Proceedings of the Fourth International Workshop on Database Programming Languages, Manhatten, New York, Workshops in Computing, pages 50--64. Springer-Verlag, February 1994.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....RPCs described in [MdS95] are generated dynamically using reflective techniques in Napier88, but they are not data type complete. For example, functions, threads or recursive values are not supported. The Octopus (Object Closure Transplantable to Other Persistent User Spaces) described in [FD94] is a reflective language mechanism developed in Napier88 that can be used to isolate portions of closures and copy them between persistent object stores. Partial closures can be rewired, possibly in a different context, using the meta level interface supplied by Octopus. This model is more ....

A. Farkas and A. Dearle. Octopus: A reflective language mechanism for object manipulation. In C. Beeri, A. Ohori, and D.E. Shasha, editors, Proceedings of the Fourth International Workshop on Database Programming Languages, Manhatten, New York, Workshops in Computing, pages 50--64. Springer-Verlag, February 1994.

.... strings to represent the code to be manipulated at run time (i.e. the source language text) later implementations have realised the limitations of this approach and have moved towards the two way split of the compiler that allows the internal form of the code to be accessed by the calling program [10, 5]. As we have seen, this is certainly an improvement over a flat source text representation, although it still falls short of the flexibility of the full modular approach. Extra transformations may be inserted into the compilation process, but only at one point (where the front end and the back end ....

A. Farkas and A. Dearle. Octopus: a Reflective Language Mechanism for Object Manipulation. In C. Beeri, A. Ohori, and D.E. Shasha, editors, Proceedings of the Fourth International Workshop on Database Programming Languages -- Object Models and Languages, pages 50--64, Manhattan, New York City, August 1993. Springer-Verlag.

....in mind. The C concept of pointers to members may be considered a restricted version of attribute references. However, the absence of runtime type information and restriction to function members, renders C pointers to members considerably less useful than attribute references. Octopus [Farkas Dearle 93] provides a reflective language mechanism for generic manipulation of complex object structures. Like the BETA MLI, the Octopus mechanism enforces static typing constraints, but does not allow the meta level programmer to express such constraints. Furthermore, Octopus provides only limited ....

A. Farkas and A. Dearle. Octopus: A Reflective Language Mechanism for Object Manipulation. In Proceedings of the Fourth International Workshop on Database Programming Languages. Springer-Verlag, 1993.

....value, the utility of the value in its new environment nor from an efficiency point of view. In order to accommodate this rebinding, bindings must first be broken which is in itself a dangerous activity. One proposal for achieving such rebinding in a safe 27 manner is that of Octopuses given in [Farkas Dearle, 1993]. This allows the bindings within a value to be broken, producing a wiring diagram of the broken bindings. This wiring diagram may then be rebound in the new environment when the value is moved. Since the wiring diagram is effectively an abstract data type it may be programmed to achieve a number ....

Farkas, A. & Dearle, A., 1993. Octopus: A Reflective Language Mechanism for Object Manipulation. In Database Programming Languages, Beeri, C., Ohori, A. & Shasha, D.E. (ed.), Springer-Verlag, Proc. 4th International Conference on Database Programming Languages, New York City pp 50-64.

....is mainly focussed on implementation issues [52,53] Persistent stores: developments in persistent store technology should give better support for bulk data. Persistent programming environments: current research into configuration management of persistent programs and novel binding schemes [24] could revolutionise persistent programming environments. Meta programming: current work on linguistic [44] and other forms of reflection [24] should lead to better application support for meta programming. Finally, there has been a tendency in the persistence research community not to make ....

....for bulk data. Persistent programming environments: current research into configuration management of persistent programs and novel binding schemes [24] could revolutionise persistent programming environments. Meta programming: current work on linguistic [44] and other forms of reflection [24] should lead to better application support for meta programming. Finally, there has been a tendency in the persistence research community not to make the tools available outside of restricted circles. We believe that this has inhibited both research into orthogonal persistence and the use of ....

A.M. Farkas and A. Dearle, "Octopus: a Reflective Language Mechanism for Object Manipulation", in Proc. 4th Intl. Workshop on Database Programming Languages, New York City, 1993.

....deep copies can sometimes be too large, up to the entire system, and may reveal sensitive information. There is a need for sending arbitrary subgraphs which need not be entirely consistent. For this we propose the mechanism of capsules, which is related to the Octopus model of Farkas and Dearle [12][13] to the substitutions of Mira da Silva [36] and to the work on adaptive parameter passing of Lopes [25] A capsule captures a portion of the state of an object system with the guarantee that no reference exists between the capsule s contents and the rest of the system. Thus a capsule contains ....

A. Farkas and A. Dearle. Octopus: A reflective language mechanism for object manipulation. In Proceedings of the Fourth International Workshop on Database Programming Languages, Lecture Notes in Computer Science. Springer-Verlag, 1993.

....programming abstractions. The type safe RPCs described in [MdS95] are generated dynamically using reflective techniques in Napier88, but are limited to simple data types (excluding functions and threads) The Octopus (Object Closure Transplantable to Other Persistent User Spaces) described in [FD94] is a reflective language mechanism developed in Napier88 that can be used to isolate portions of closures and copy them between persistent object stores. Partial closures can be rewired, possibly in a different context, using the meta level interface supplied by Octopus. This model is more ....

A. Farkas and A. Dearle. Octopus: A reflective language mechanism for object manipulation. In C. Beeri, A. Ohori, and D.E. Shasha, editors, Proceedings of the Fourth International Workshop on Database Programming Languages, Manhatten, New York, Workshops in Computing, pages 50--64. Springer-Verlag, February 1994.

....it cannot be effectively used to save anything other than entire object closure. In many persistent systems the object closure may include the entire persistent store and perhaps even large portions of the Internet. If this approach is to be followed, techniques such as Farkas OCTOPUS mechanism [4] or the use of weak pointers are also required. The next approach to saving state is to provide persistence at the (Java) virtual machine level. This is the approach followed by Atkinson s PJava group [2] Whilst we have argued elsewhere that the last approach is better, this approach has many ....

Farkas, A. and A. Dearle. Octopus: A Reflective Language Mechanism for Object Manipulation. in Proceedings of the Fourth International Workshop on Database Programming Languages. 1994: Spinger_Verlag.

....thus facilitating software component and data distribution. Partial closures may be cut from one location and rewired in another, possibly in a different context, using the interface supplied by Octopus. A brief description of Octopus is given in this section, and the reader is referred to [5] for a more detailed discussion on the use of this mechanism. The essence of the Octopus mechanism is to allow values from the programming language value space to be hoisted up to a meta level and manipulated in ways which the programming language would not otherwise permit. This is achieved using ....

Farkas, A. and Dearle, A. "Octopus: A Reflective Language Mechanism for Object Manipulation", in The Proceedings of the Fourth International Workshop on Database Programming Languages, Springer-Verlag, New York City, 1993.

....and manipulating bindings, Section 3 describes a mechanism for propagating type changes through existing programs, Section 4 describes Nodules and section 5 describes how these mechanisms form a part of the programming environment. 2 Octopus A mechanism called Octopus is described in [5] and [6] which allows all bindings in an arbitrary graph of objects to be examined and manipulated. In essence, Octopus provides a uniform viewing mechanism with which values and bindings of any type may be viewed and manipulated using the same set of operations. The mechanism allows values to be hoisted ....

Farkas, A. and Dearle, A. "Octopus: A Reflective Language Mechanism for Object Manipulation", in Proceedings of the Fourth International Workshop on Database Programming Languages, New-York, Springer-Verlag, 1994.

No context found.

A. Farkas and A. Dearle. Octopus: A reflective language mechanism for object manipulation. In C. Beeri, A. Ohori, and D.E. Shasha, editors, Proceedings of the Fourth International Workshop on Database Programming Languages, Manhatten, New York, Workshops in Computing, pages 50--64. Springer-Verlag, February 1994.

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