A.M. Farkas and A. Dearle, The Octopus Model and its Implementation, 17th Australasian Computer Science Conference, pp. 581-590, 1994.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....The concept of subsystem exists in a restricted form in many OO frameworks. An aggregate in Fusion [19] is a group of classes, associations and attributes (but not operations, at the analysis level) used to model a part of relationship or to identify a relationship as an entity. In Octopus [23] aggregations are used to partition an application into functional sub applications, rather like the domain concept of Syntropy [21] UML provides two forms of aggregation to designate part whole relationships, both considered to be particular uses of associations. Whilst the meaning of the strong ....

A.M. Farkas and A. Dearle, The Octopus Model and its Implementation, 17th Australasian Computer Science Conference, pp. 581-590, 1994.

....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 ....

....encapsulated values. The ability of Octopus to access encapsulated bindings requires special attention in the implementation architecture. To illustrate this, we will describe how the partsDatabase application is represented and how Octopus manipulates this representation. Readers are referred to [5] for a more detailed description of the Octopus architecture. In systems supporting Octopus, all bindings encapsulated in procedures are stored separately from executable code. All procedural values are represented by two entities: a structure containing only executable code, known as a code ....

Farkas, A. and Dearle, A. "The Octopus Model and its Implementation", in Proceedings of the 17th Australian Computer Science Conference, Australian Computer Science Communications, vol 16, pp. 581-590, 1994.

....RISC architectures such as the DEC Alpha [15] We expect to have a robust native code generator running on an Alpha platform by the time this paper is published. 7 Future Work We are currently investigating the use of boxed values [13] as implemented in the interpreted Napier88 Octopus system [8] . We believe that the use of boxed values will permit lazy code, as described in Section 3.7, to be generated in many more cases than is currently possible. Whether or not this proves to be an optimisation remains to be seen. We are currently assembling Napier88 systems that will permit us to ....

.... will support independent configuration of the following options: whether the store is directly mapped with page granularity, or swizzed with object granularity; whether the code in the store is native code or interpreted PAM code; whether the code in the store uses the Octopus model [8] or the original PAM frame model [4] and . whether the system will run on the Sun SPARC architecture or the DEC Alpha AXP architecture. We plan to measure the performance of the OO7 benchmark [3] under all combinations of the above options, comparing object swizzled and page mapped stores. ....

Farkas, A. and Dearle, A. "The Octopus Model and its Implementation", 17th Australian Computer Science Conferenc , Australian Computer Science Communications, vol 16, pp. 581590, 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