Morrison, R., A.L. Brown, R.C.H. Conor, A. Dearle "The Napier88 Reference Manual" Technical report PPRR-77-89 University of St Andrew, St Andrew,1989  Home/Search   Document Not in Database   Summary   Related Articles   Check

....and hence component re use. Nonetheless, parameterised polymorphism is provided in few languages in other paradigms. As ever there are exceptions to this rule including the addition of generics to object oriented languages like Java [7, 8, 9] the Napier imperative persistent database language [10]; and Prolog[11] a strongly typed Prolog variant used for theorem proving. We suspect that this apparent resistance to including polymorphic type systems in contemporary languages lies in a combination of unfamiliarity, and the aura of complexity and mathematical sophistication surrounding such ....

Morrison R., Brown F., Connor R and Dearle. A. (1989) The Napier88 Reference Manual. Persistent Programming Research Report 77, University of St Andrews/Un iversity of Glasgow.

....accesses involve several file seek and read operations. The second of these two problems may be addressed using memory mapping techniques as discussed in the following section. 2.2. Memory mapping techniques 2.2. 1 Using SunOS memory mapped files Support for persistence in the Napier88 system [28] has, to date, been provided using two different techniques [15, 16] The first uses a much simplified CPOMS approach, the other uses SunOS memory mapped files. We will discuss this second implementation here. The Stable Store which implements a resilient persistent address space as discussed in ....

Morrison, R., Brown, A. L., Conner, R. C. H. and Dearle, A. "Napier88 Reference Manual", Universities of Glasgow and St. Andrews, Persistent Programming Research Report PPRR- 77-89, 1989.

....are simply typed objects, including scalars, structures and arrays which may stored and retrieved in a type secure manner. Higher level structures can be built by using mechanisms provided by the programming language. Some persistent systems do directly support encapsulated objects (e.g. Napier88 [44] and Monads [51] However, most do not (as yet) support any notion of inheritance. It is interesting to reflect on the differences between conventional object oriented languages and a persistent object oriented language. In a language such as C [56] support for objects and encapsulation can ....

Morrison, R., Brown, A. L., Conner, R. C. H. and Dearle, A. "Napier88 Reference Manual", Universities of Glasgow and St. Andrews, Persistent Programming Research Report PPRR-77-89, 1989.

.... is the ability for program data to endure longer than the invocation of the program which creates it [2] It has formed the basis for a large research community which has identified the underlying principles of persistence and led to the construction of a number of persistent programming languages [1, 19, 22, 24, 27]. The resulting languages have been diverse, conforming to no common design principle for the paradigm. Thus we have languages ranging from the general purpose PS algol [15] to the capability architecture of c [18] and the functional programming language Staple [21] Thus it seems that ....

R. Morrison, F. Brown, R. Connor and A. Dearle, "The Napier88 Reference Manual", Persistent Programming Research Report 77, Universities of Glasgow and St. Andrews Computer Science Departments (July 1989).

.... thesaurus tool was developed for a health management system (HMS) in an industrial (C, C , X Window System and relational database) environment (Sj berg 1993a) Another thesaurus tool was thereafter built in the research context of the strongly typed, persistent programming language Napier88 (Morrison et al. 1989). The concept of persistence tackles the mismatch between database systems and programming languages (Atkinson 1978) a uniform model for representations and operations on persistent and transient data is provided. Some of the features of the thesaurus tools are: structure and dependency ....

Morrison, R., Brown, F., Connor, R. and Dearle, A. (1989). The Napier88 Reference Manual. Technical Report PPRR-77-89, Universities of Glasgow and St Andrews.

....and its migration into other clients. Using this vehicle, the coherency protocol and client server architecture are illustrated and explained. 1 Introduction This paper describes a distributed architecture designed to support applications written in the persistent programming language Napier [1]. The Napier programmer views the world as a graph of strongly typed, stable persistent objects known as the persistent store. In this domain of discourse, all the physical properties of data have been abstracted over; examples of such properties include the location of the data, i.e. whether it ....

Morrison R., Brown A.L., Connor R. & Dearle A. "The Napier88 Reference Manual". Universities of Glasgow & St Andrews Persistent Programming Research Report 77-89 (1989).

....ends of the design spectrum where as model 2 is a hybrid architecture. These models are described in the following sections. 3. 1 Single flat address space In the first model all data resides in a single flat address space, this is the model adopted by the Napier88 persistent programming system [28]. The construction of very large stores using this technique was not feasible on conventional architectures until recently due to address size limitations. However, the advent of machines such as the DEC Alpha [35] and the MIPS R4000 [17] which (logically) support a 64 bit address has created ....

Morrison, R., Brown, A. L., Connor, R. C. H. and Dearle, A. "The Napier88 Reference Manual", PPRR-77-89, 1989.

No context found.

Morrison, R., Brown, A. L., Connor, R. C. H. et al. (1994) The Napier88 Reference Manual (Release 2.0). University of St Andrews.

No context found.

Morrison, R., Brown, A.L., Connor, R.C.H. & Dearle, A. "The Napier88 Reference Manual". University of St Andrews Technical Report PPRR-77-89 (1989).

.... for example, PMOS [11] The initial implementation of Lumberjack is proceeding in parallel with the writing of this paper and serves a number of purposes: It delivers object based logging for use on conventional operating systems and is intended to support applications such as Napier88 [9] and persistent Java [2] It provides a platform that enables empirical comparisons to be made between log structured store designs and the various alternatives. This is significant because the use of log structured storage is relatively new in the field of persistent systems and it would be ....

R. Morrison, A.L. Brown, R.C.H. Connor, and A. Dearle, "The Napier88 Reference Manual", Technical Report PPRR-77-89, University of St. Andrews, St. Andrews, 1989.

....and tools. In particular, persistent store browsers [4,7,8,14] have been developed which permit users to discover the types of values contained in a persistent store, and the structure of values with respect to each other. In systems such as the Aberdeen programming environment [8] for Napier88 [17], the browser enables a user to quickly locate and execute programs in a persistent store without prior knowledge of the location of the data, programs or their interfaces. This is achieved by displaying graphical representations of the discovered values and their types. Using this information the ....

Morrison, R., Brown, A. L., Connor, R. C. H. and Dearle, A. "The Napier88 Reference Manual", University of St Andrews, Technical Report PPRR-77-89, 1989.

....file seek and read operations. The second of these two problems may be addressed using memorymapping techniques as discussed in the following section. RT1R1 2 4 23 09 98 1.1.2# Memory mapping techniques 1.1.2. 1# Using SunOS memory mapped files Support for persistence in the Napier88 system [32] has, to date, been provided using several techniques [7] The first uses a much simplified CPOMS approach, the other uses SunOS memory mapped files. We will discuss this second implementation here. The Stable Store which implements a resilient persistent address space as discussed in section ....

R. Morrison, A.L. Brown, R.C.H. Connor, and A. Dearle, "The Napier88 Reference Manual", Technical Report PPRR-77-89 URL: http://www-fide.dcs.stand. ac.uk/Publications/1989.html#napier.reference.manual, Universities of Glasgow and St Andrews, 1989.

....of problems associated with them. Firstly, as we have demonstrated above, the high level abstractions provided by monolithic systems, such as Unix, are inappropriate for the construction of persistent systems. This is evidenced by the sheer size of the persistent systems (for example Napier88 [43], PS algol [1] or Pjama [6] that have been implemented using them. Much of the complexity of these systems is due to the engineering of idealised virtual machines above inappropriate platforms. Secondly, the evolution of monolithic kernels is extremely difficult due to the combination of poor ....

R. Morrison, A.L. Brown, R.C.H. Connor, and A. Dearle, "The Napier88 Reference Manual", Technical Report PPRR-77-89 URL: http://www-fide.dcs.stand. ac.uk/Publications/1989.html#napier.reference.manual, Universities of Glasgow and St Andrews, 1989.

....efficacy of a persistent object store as a base technology for an integrated programming environment. Other points of interest are the effectiveness of parametric polymorphism, 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 ....

Morrison, R., Brown, A. L., Connor, R. C. H. and Dearle, A. "The Napier88 Reference Manual", University of St Andrews Technical Report PPRR-77-89, 1989.

....of a fully template based editor. The underlying representation of the program components should be structured, probably tree structured, at some level of abstraction. Thus, selecting some part of a program component amounts to selecting some subtree. For example, Figure 2 shows a Napier88 [5] program component; part of the component has been selected by the user. This part corresponds to a complete subtree in the underlying structured representation of the program component. Because a complete subtree must be selected, it is not possible to select only the keyword type ; selecting ....

Morrison, R., Brown, F., Connor, R. and Dearle, A. "The Napier88 Reference Manual", University of St Andrews, PPRR-77-89, 1989.

....: proc( Octopus Value ) In the procedure signatures above, the value hoisted to and dropped from an Octopus has the type Value. Since values of any type may be represented as an Octopus, the type Value must be an infinite union type, and type checking must be performed dynamically. In Napier88 [11], this functionality is delivered by the infinite union type any, into which values of any type may be injected. Values encapsulated in an any are type compatible with each other even if the encapsulated values are of different types. In the Octopus model all values conceptually have special ....

Morrison, R., Brown, A. L., Connor, R. and Dearle, A. "The Napier88 Reference Manual", University of St. Andrews, PPRR-77-89, 1989.

....programs may create data structures which outlive their execution and there is no need to write code to flatten data structures in order to store them in files. A number of persistent systems have been constructed, most of which have been built above conventional operating systems, usually Unix [1,4,25,26,32]. Although these systems have been successful in terms of demonstrating the feasibility of persistence as a programming paradigm, efficiency has been a major problem. This is not surprising since they are being constructed above operating systems with a model that is fundamentally different from ....

Morrison, R., Brown, A. L., Conner, R. C. H. and Dearle, A. "Napier88 Reference Manual ", Universities of Glasgow and St. Andrews, Persistent Programming Research Report PPRR-77-89, 1989.

....stores must be intimately bound with respect to store stabilisation. If the stores did not stabilise synchronously, the semantics of failure in a persistent system would be unpredictable. 4. Napier88 In order to illustrate our communication mechanism we will use the language Napier88 [MBC89] as a framework. However, the mechanisms described in this paper may be incorporated into any programming language which supports at least first class procedures, parametric polymorphism and some global contextual naming facility. In the context of the Napier88 programming language, these ....

Morrison, R., Brown, A.L., Connor, R. & Dearle, A. "The Napier88 Reference Manual". PPRR-- 77--89, Universities of St Andrews and Glasgow, Scotland (1989).

....are: DBPL [MS89] relational . PS algol [PS88] imperative . Leibniz [Eve85] object . E [RC89] almost object (C ) Galileo [ACO85] object . Poly [Mat85] applicative . Staple [DM90] applicative . Amber [Car85] applicative . Persistent Prolog [GMD85] logic . c [HS89] capability . Napier88 [MBC89] imperative 1.2.4.1 PS algol and Napier88 Two examples of orthogonally persistent languages are PS algol [PS88] and Napier88 [MBC89] In both languages, persistence is identified by reachability from distinguished roots in a persistent store. For a value to persist after the invocation of a ....

....[ACO85] object . Poly [Mat85] applicative . Staple [DM90] applicative . Amber [Car85] applicative . Persistent Prolog [GMD85] logic . c [HS89] capability . Napier88 [MBC89] imperative 1.2.4. 1 PS algol and Napier88 Two examples of orthogonally persistent languages are PS algol [PS88] and Napier88 [MBC89]. In both languages, persistence is identified by reachability from distinguished roots in a persistent store. For a value to persist after the invocation of a program, it must be placed within the transitive closure of one of these distinguished roots. This model of persistence is highly suitable ....

[Article contains additional citation context not shown here]

R. Morrison, A.L. Brown, R.C.H. Connor and A. Dearle "The Napier88 Reference Manual" University of St Andrews PPRR-77-89 ( 1989 )

....provide encapsulation and protection of data. The power of traditional library facilities, modules and generics are subsumed when first class procedures are combined with persistence and a powerful type system that includes parametric polymorphism. In this paper, the programming language Napier88 [13] is used as the vehicle to describe the incremental system construction methodology. It has first class procedures, assignment, orthogonal persistence and a polymorphic type system. This paper describes an incremental method of system construction. A simple example is introduced and used ....

Morrison, R., Brown, A. L., Connor, R. C. H. and Dearle, A. "The Napier88 Reference Manual", University of St Andrews, PPRR-77-89, 1989.

....of the browser for future use. This technique requires two facilities in the programming language. Firstly, since the browser program can take any data type as a parameter, some dynamic type checking is required. This may be satisfied using a type such as dynamic in Quest [4] or any in Napier88 [18]. The second requirement is that the reflective part of the language has the ability to deliver the type of the value supplied to the browser. In Napier88 this is achieved through the use of a special function which delivers a representation of the type of a value encapsulated in an any. Making ....

Morrison, R., Brown, A. L., Connor, R. and Dearle, A. "The Napier88 Reference Manual", University of St. Andrews, PPRR-77-89, 1989.

....of a fully template based editor. The underlying representation of the program components should be structured, probably tree structured, at some level of abstraction. Thus, selecting some part of a program component amounts to selecting some subtree. For example, Figure 2 shows a Napier88 [5] program component; part of the component has been selected by the user. This part corresponds to a complete subtree in the underlying structured representation of the program component. Because a complete subtree must be selected, it is not possible to select only the keyword type ; selecting ....

Morrison, R., Brown, F., Connor, R. and Dearle, A. "The Napier88 Reference Manual", University of St Andrews, PPRR-77-89, 1989.

....of persistent, algorithmic, object oriented and applicative programming languages currently in use, as well as being sufficiently flexible to be used as an experimental platform. However, the original motivation for constructing the architecture was to support the persistent language Napier88 [Morrison, et al. 1989] . The model of persistent store supported by Casper is a conceptually infinite, shared and resilient data store. The aim of the architecture described in this paper is to support concurrent access to the persistent store by users on workstations connected by a local area network. This model of ....

Morrison, R., Brown, A. L., Connor, R. C. H. & Dearle, A., "The Napier88 Reference Manual", University of St Andrews, 1989.

....we demonstrate how the mechanisms provided by Grasshopper may be used to implement a persistent version of the language Java. 1. Introduction Over the last ten to fifteen years we have seen a number of persistent language systems. Some of these were designed to be persistent from the outset [3, 19], others are persistent versions of ordinary programming languages e.g. 21] What these language systems have in common is that they have been implemented as separate language systems above a non persistent operating system. It is our belief that, although persistence can be implemented by a ....

Morrison, R., Brown, A. L., Connor, R. C. H. and Dearle, A. "The Napier88 Reference Manual", University of St Andrews, Technical Report PPRR-77-89, 1989.

No context found.

Morrison, R., A.L. Brown, R.C.H. Conor, A. Dearle "The Napier88 Reference Manual" Technical report PPRR-77-89 University of St Andrew, St Andrew,1989

First 50 documents

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