Kirby G.N.C., Connor R.C.H., Cutts Q.I., Dearle A., Farkas A. & Morrison R. "Persistent Hyper-Programs" Proc. 5th International Workshop on Persistent Object Systems, San Miniato, Italy, September 1992, in Persistent Object Systems, San Miniato 1992, Springer-Verlag, pp 86 - 106.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... demonstrated that persistence allows for the development of software in a markedly different manner than conventionally might be possible, especially when combined with reflection [DOW94] Other interesting work has included the explorion of hyperprogramming systems within a persistent environment [KCC92]. This has also demonstrated that persistence is a useful tool, when combined with other novel features such as a compiler which is callable from within a program itself. The application of persistence outside of the usual programming domain has been explored through the development of a ....

G.N.C. Kirby, R.C.H. Connor, Q.I. Cutts, A. Dearle, A.M. Farkas and R. Morrison, "Persistent Hyper-Programs", 5th International Workshop on Persistent Object Systems, San Miniato, Persistent Object Systems, SpringerVerlag, Workshops in Computing, pp. 86-106, 1992.

....systems with a strong requirement for evolution. Linguistic reflection enhances support for prototyping by allowing interactive programming, data visualisation[18] and application generator tools[17] to be built. It also supports advanced software construction techniques such as hyper programming[19, 24], and is useful for building applications that operate at the meta program or metadata level. We have identified a problem common to most examples where persistence support has been added to an existing programming language; namely that the persistence mechanims breaks the language s data ....

G.N.C. Kirby, R.C.H. Connor, Q.I. Cutts, A. Dearle, A. M. Farkas, and R. Morrison. Persistent hyper programs. In Proceedings 5th International Workshop on Persistent Object Systems, San Miniato, Italy, September 1992.

....it is a small step to provide a compiler that can be invoked at runtime; i.e. a callable compiler. A callable compiler allows the programmer to use reflective programming techniques. Combining reflection with persistent source code representations leads to interesting ideas like hyperprogramming (Kirby, Connor, Cutts, Dearle, Farkas, and Morrison 1992). Another idea that is currently being explored in conjunction with persistent programming is reification or meta programming. The basic idea of reification is that values and types can be lifted to a meta programming level where normal types can be treated as values and normal values can be ....

Kirby, G. N. C., R. C. H. Connor, Q. I. Cutts, A. Dearle, A. M. Farkas, and R. Morrison (1992, September). Persistent hyper programs.

....will invoke further typechecking. Other significant uses of any are: 1. to allow code to be written which will handle data not yet specified; 2. to provide an interface for type enquiry when generating type safe code that provides type dependent behaviour via reflection [Dearle and Brown, 1988; Kirby, 1992; Stemple et al. 1992] 3. to act as place holders for parts of schemata that are yet to be specified while code operates against the parts already defined. The type env in Napier88 denotes an updateable set of bindings [Dearle, 1989] Each binding holds an identifier, a locality in which a ....

.... and verification earlier, e.g. this leads to early feedback to 4 A particular program is usually concerned only with data described by some small subgraph of the schema against which it runs programmers, to further reduction in text input and checking costs, and to novel program structures [Kirby et al. 1992; Farkas et al. 1992] A recurring interest in the type system research for persistent languages is the appropriate treatment of bulk types [Atkinson and Buneman, 1987] These types describe regular structures such as: sets, relations, finite maps, sequences and trees. The description is ....

G. Kirby, R. Connor, Q. Cutts, A. Dearle, A. Farkas, and R. Morrison. Persistent hyper-programs. In A. Albano and R. Morrison, editors, Fifth International Workshop on Persistent Object Systems. Design, Implementation and Use (San Miniato, Italy, 1st-4th September 1992), 1992.

No context found.

Kirby G.N.C., Connor R.C.H., Cutts Q.I., Dearle A., Farkas A. & Morrison R. "Persistent Hyper-Programs" Proc. 5th International Workshop on Persistent Object Systems, San Miniato, Italy, September 1992, in Persistent Object Systems, San Miniato 1992, Springer-Verlag, pp 86 - 106.

....below, this process may be performed at a variety of times. 3 . 2 Accessing Client Code The example above has indicated broadly how name and type servers may be used co operatively. The task of accessing the client code used to invoke a container may generally occur at three different times [9,13]: 1. Firstly, it is possible for the programmer to interrogate a name and type server during client construction. The interfaces to the various required containers may be discovered, and code constructed to call the correct interface procedures. The client code may be copied from a type server ....

....for a variety of circumstances. Each implementation could be tagged with a set of attributes denoting information such as garbage collection style, page alignment, whether free lists are used, and so on. 5 . 3 Hyper Programming and Browsers Hyper programming has been described in various places [9,12,13], and is currently implemented in several Napier88 systems. The essence of hyper programming is to allow a user to indicate that a program or value in the persistent store should be included directly within the source code of a program; this process is analogous to the way in which entities are ....

Kirby, G. N. C., Connor, R. C. H., Cutts, Q. I., Dearle, A., Farkas, A. M. and Morrison, R. "Persistent HyperPrograms ", 5th International Workshop on Persistent Object Systems, San Miniato, Persistent Object Systems, Springer-Verlag, Workshops in Computing, pp. 86-106, 1992.

....by a program may already be available in the persistent store. Since the program itself is a persistent object, it can include direct links to such objects rather than textual descriptions of how to locate the objects. A program containing both text and links to objects is called a hyper program [1]. Figure 1 shows an example hyper program that contains a link to another persistent object. The analogy with hyper text is made by the links being displayed as buttons. The programmer can follow these links using a browsing tool, to reveal further hyper programs and other data structures. ....

....programmer can follow these links using a browsing tool, to reveal further hyper programs and other data structures. object program text . let x = persistent store object object hyper program Figure 1. Example hyper program The benefits of hyper programming are discussed in [1 3]. They include: being able to perform program checking early . support for source representations of all object closures . being able to enforce associations from executable programs to source programs . availability of an increased range of linking times . increased program succinctness . ....

G.N.C. Kirby, R.C.H. Connor, Q.I. Cutts, A. Dearle, A.M. Farkas and R. Morrison. Persistent Hyper-Programs. In A. Albano and R. Morrison (ed) Persistent Object Systems, Proc. 5th International Workshop on Persistent Object Systems (POS5), San Miniato, Italy. Springer-Verlag, 1992, pp 86-106.

....reflection and the provision of a compiler that may be invoked at run time. These features are all available in Napier88 [23] our chosen implementation language. Initially, a hyper programming system was constructed in which arbitrary values from the object store may be bound to program source [18]. These values may include other program fragments in systems like Napier88 that support first class procedures and functions. Hyper links [10] to program documentation are also supported in the PIPE system. Documentation may contain hyperlinks to other documentation or program fragments. Thus the ....

Kirby, G. N. C., Connor, R. C. H., Cutts, Q. I., Dearle, A., Farkas, A. M. and Morrison, R. "Persistent Hyper-Programs", 5th International Workshop on Persistent Object Systems, San Miniato, pp.86-106 1992.

....the applications programmer. Hyperprogramming is a further step in this direction and the paper explores how effective the concept can be in different environments. 2. 1 Constructing Hyper programs The primary motivation for hyper programming is to allow the user to compose programs interactively [3, 4], navigating the environment and selecting data items, including code, to be incorporated into the programs. This removes the need to write access specifications for extant data items that are used by a program. For example, in a file system it may be a path name, and in a persistent object store ....

....types will always remain compatible. Where a link denotes a location, that location is linked directly into the executable program produced from the hyper program, so that updates to the location also affect the executable program. 2. 3 Experience The benefits of hyper programming described in [1, 3, 4] may be summarised as: being able to perform program checking early . support for source representations of all object closures . being able to enforce associations from executable programs to source programs . availability of an increased range of linking times . increased program ....

[Article contains additional citation context not shown here]

Kirby G.N.C., Connor R.C.H., Cutts Q.I., Dearle A., Farkas A.M., Morrison R. Persistent Hyper-Programs. In: A. Albano and R. Morrison (ed) Persistent Object Systems, Proc. 5th International Workshop on Persistent Object Systems (POS5), San Miniato, Italy. Springer-Verlag, 1992, pp 86-106

....for a type. The nature of these representations is described in more detail in Section 3. The getSource operation returns a representation of the source code for the value. If the value is a procedure, this source code is similar to the hyper program model of source code described in [6] 7] and [8]. If the value encapsulated in an Octopus is not a procedure, then getSource returns a representation of the value which is suitable for use in hyper programs. A scan procedure is provided to iterate over the bindings contained in an Octopus; scan takes as its single parameter a programmer ....

Kirby, G. N. C., Connor, R. C. H., Cutts, Q. I., Dearle, A., Farkas, A. and Morrison, R. "Persistent Hyper-Programs", in The Proceedings of the Fifth International Workshop on Persistent Object Systems, Pisa, pp. 86-106, 1992.

....orthogonally persistent system. The system was also intended as, or turned out to be, a testbed for experiments in: type systems for data modelling [2 7] bulk data [8, 9] and protection [10, 11] programming language implementation [12, 13] binding mechanisms [14 17] programming environments [17 20]; system evolution [21 23] concurrency control and transactions [24 27] object stores [26, 28 35] and software engineering tools [36 39] The Napier88 system consists of the Napier88 language [40] and its persistent environment [41] The persistent store comes pre populated, rather like the ....

....name spaces to be placed over the value space enabling applications to utilise their private persistent name space while sharing values in the persistent store. The syntactic noise involved in using the persistent store, through project and use clauses, may be reduced by hyper programming [20] which allows values to be directly linked to source code at composition time. Thus the navigational code and type specifications need not always be included in the program. 4 Data Modelling Type systems provide two important facilities within both databases and programming languages, namely ....

[Article contains additional citation context not shown here]

Kirby GNC, Connor RCH, Cutts QI, Dearle A, Farkas AM, Morrison R. Persistent Hyper-Programs. In: Albano A, Morrison R (ed) Persistent Object Systems, Proc. 5th International Workshop on Persistent Object Systems (POS5), San Miniato, Italy. Springer-Verlag, 1992, pp 86-106

No context found.

G. N. C. Kirby, R. C. H. Connor, Q. I. Cutts, A. Dearle, A. M. Farkas and R. Morrison, `Persistent HyperPrograms ' In Persistent Object Systems, A. Albano and R. Morrison (ed), Springer-Verlag, Proceedings of the 5th International Workshop on Persistent Object Systems, San Miniato, Italy, 86-106 (1992).

....using these functions, the programmer can obtain any required information about the type. The getSource operation returns a representation of the source code for the value. If the value is a procedure, this source code is similar to the hyperprogram model of source code described in [9] 13] and [14]. If the value encapsulated in an Octopus is not a procedure, then getSource returns a representation of the value which is suitable for use in hyper programs. The model of source representation is the topic of related research and will not be discussed further in this paper. A scan procedure is ....

....architecture is the topic of another paper. In the current prototype of the system described in this paper, the source code obtained from an Octopus is a linear textual representation. Our intention is to extend the source code representation to support the features offered by hyperprogramming [13, 14]. In addition, by allowing partially resolved hyper programs to exist, a method of template programming [10] may be developed. These techniques appear to be complementary to the ideas presented in this paper. In this paper a mechanism which provides a uniform abstract interface to values of any ....

Kirby, G. N. C., Connor, R. C. H., Cutts, Q. I., Dearle, A., Farkas, A. and Morrison, R. "Persistent Hyper-Programs", in Proceedings of the Fifth International Workshop on Persistent Object Systems, Pisa, pp. 86-106, 1992.

....construction [4] and component reuse [9] by allowing components to be created, stored in the persistent object store and bindings between them established. Bindings may be established at different times: during program construction, at program compile time and when the program is executing [7]. 1 Throughout this paper, the terms program, procedure and functions are used synonymously. type Part is structure( name : string ; id,quantity : int ) The database is encapsulated within the partsDatabase procedure whose parameters are a command, a part name and a quantity. let ....

....: proc( string Binding ) scan : proc( proc( Binding ) Figure 2: The structure of an Octopus. The getSource operation returns a representation of the source code for the value. If the value is a procedure, this source code is similar to the hyper program model of source code described in [7]. If the value encapsulated in an Octopus is not a procedure, then getSource returns a representation of the value which is suitable for use in hyper programs. The getBinding operation returns the binding associated with the given name if one exists. A scan procedure is provided to iterate over ....

Kirby, G. N. C., Connor, R. C. H., Cutts, Q. I., Dearle, A., Farkas, A. M. and Morrison, R. "Persistent Hyper-Programs", 5th International Workshop on Persistent Object Systems, San Miniato, Persistent Object Systems, Springer-Verlag, Workshops in Computing, pp. 86-106, 1992.

....times includes just before use dynamic checking. At the other end of the spectrum the presence of the persistent store allows persistent values to be bound to programs during program construction. Where the programs themselves are persistent objects, this leads to the concept of hyper programming [Kirby et al. 1992] that will be discussed later. For the present it is sufficient to realise that persistent values are available to the type checker allowing types to be value based. This leads to persistent systems being able to support some dependent types (i.e. types which require tests on values to establish ....

....belong to category 1 which up until now in not much used in programming systems. The advantage of this style of binding has already been shown in dependent types and will be shown later to lead to the concept of hyperprogramming: a new technology only available in orthogonally persistent systems [Kirby, et al. 1992]. Persistent systems also highlight the need to break bindings and to recreate them later or in some other context. Consider the problem of releasing systems. In order to ship a system from one environment to another it is often sensible to ensure that the system fits in with the new environment. ....

[Article contains additional citation context not shown here]

Kirby, G.N.C., Connor, R.C.H., Cutts, Q.I., Dearle, A., Farkas, A.M. & Morrison, R., 1992. Persistent Hyper-Programs. In Persistent Object Systems, Albano, A. & Morrison, R. (ed.), Springer-Verlag, Proc. 5th International Workshop on Persistent Object Systems, San Miniato, Italy pp 86-106.

No context found.

Kirby, G.N.C., Connor, R.C.H., Cutts, Q.I., Dearle, A., Farkas, A.M. & Morrison, R. "Persistent Hyper-Programs". In Persistent Object Systems, Albano, A. & Morrison, R. (ed), SpringerVerlag, Proc. 5th International Workshop on Persistent Object Systems, San Miniato, Italy (1992) pp 86-106.

No context found.

* Kirby, G.N.C., Connor, R.C.H., Cutts, Q.I., Dearle, A., Farkas, A.M. & Morrison, R. "Persistent Hyper-Programs". In Persistent Object Systems, Albano, A. & Morrison, R. (ed), Springer-Verlag, Proc. 5th International Workshop on Persistent Object Systems, San Miniato, Italy (1992) pp 86-106.

No context found.

Kirby, G.N.C., Connor, R.C.H., Cutts, Q.I., Dearle, A., Farkas, A.M. & Morrison, R. "Persistent Hyper-Programs". In Persistent Object Systems, Albano, A. & Morrison, R. (ed), Springer-Verlag (1992) pp 86-106.

....various times at which identifiers embedded in a program are resolved to their associated values, as follows: During program composition. The source contains embedded values. During compilation these values are incorporated into the compiled code. This technique is known as hyper programming [KCC 92] During compilation. Free identifiers in the source are resolved using values passed into the compiler [FDK 92] Between compilation and execution. The resolution of the identifiers is performed in a separate phase involving an intermediate program representation and the associated values. ....

....by navigating the persistent environment and selecting data items to be bound into the programs. This requires that direct links to persistent data items are contained in program source code and that the compiler can manipulate such links. This style of programming is known as hyper programming [KCC 92] and has been implemented on top of the integrated programming environment described here [Kir92] Browsing technology Advanced persistent object browsers [DCK90,FDK 92] have been developed using the technology described in this thesis. In particular, the ABERDEEN environment developed at the ....

[Article contains additional citation context not shown here]

G.N.C. Kirby, R.C.H. Connor, Q.I. Cutts, A. Dearle, A.M. Farkas and R. Morrison "Persistent Hyper-Programs" In Proc. 5th International Workshop on Persistent Object Systems, San Miniato, Italy (1992) pp 73-95.

No context found.

Kirby, G.N.C., Connor, R.C.H., Cutts, Q.I., Dearle, A., Farkas, A.M. & Morrison, R. "Persistent Hyper-Programs". In Proc. 5th International Workshop on Persistent Object Systems, San Miniato, Italy (1992) pp 73-95.

....used previously did not offer initialising declarations. environment must be made. As Figure 2 reveals, most of the 20 will be concerned with these bindings. Once the complete programming exercise may be carried out within the persistent environment, new technologies such as hyper programming [38] may be used to remove almost all of this code. Second, even in the integrated persistent environment, such code may still be required when constructing programs in isolation from the data over which they will operate, for example constructing code in one store to be executed against another store ....

....within a single persistent environment. The separate processes of program construction, compilation, linking and execution may all be performed within the environment. The advantages of such a construction environment are described in [25] Of interest here is the hyper programming concept [38], where links to values and locations already existing in the persistent store may be included directly in source programs under construction. By analogy with hyper text, a hyper program is a structured version of the traditional flat source code representation that contains both flat code and ....

Kirby G, Connor R, Cutts Q, Dearle A, Farkas A, Morrison R. Persistent HyperPrograms. In: [2], pp 86--106

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