The Napier Type System

Morrison, Ronald; Brown, A. L.; Carrick, R.; Connor, Richard; Dearle, Alan; Atkinson, Malcolm

doi:10.1007/978-1-4471-3173-1_1

Cited by 20 publications

(4 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This is achieved mainly by static analysis during compilation, but flexibility is achieved by a judicious leavening of dynamic checks. 64 The principle of persistence independence ensures that this type safety extends to all long-term data. There are no loopholes in this safety regime.…”

Section: Strong Typingmentioning

confidence: 99%

Exploiting Persistence in Build Management

Sjøberg¹,

Welland

Atkinson

et al. 1997

Softw: Pract. Exper.

View full text Add to dashboard Cite

SUMMARYA challenging issue in the construction and maintenance of large application systems is how to determine which components need to be rebuilt after change, when and in which order. Rebuilding is typically recompilation and linking, but may also include update of derivable components such as cross-reference databases and re-creation of library indexes. Type definitions or schema, and data values in a file store, database or persistent store may also need to be rebuilt. The main purpose of this paper is to describe how persistent language technology can be exploited to enhance build management. In particular, the paper describes a method for transactional, incremental linking and the implementation of its support. To help implement this method, and to make it safer and more efficient to carry out rebuild activities in general, we have defined a set of automatically checkable constraints on the software. The build management tool we have implemented, the Builder, derives rebuild dependencies automatically and offers partitioning of dependency graphs-a means to defer or avoid unnecessary rebuilding. The Builder is implemented in a persistent programming language and provides build management for applications written in the language. It exploits features such as strong typing, runtime linguistic reflection, and referential integrity provided by the language processing technology. The Builder operates over both programs and (complex) data, which is in contrast to conventional language-centred tools.

show abstract

Section: Strong Typingmentioning

confidence: 99%

Exploiting Persistence in Build Management

Sjøberg¹,

Welland

Atkinson

et al. 1997

Softw: Pract. Exper.

View full text Add to dashboard Cite

show abstract

“…Most persistent systems implement the abstraction of persistent data at the programming-language level [3,18,20] and, as a result, have suffered from two drawbacks:…”

Section: Orthogonal Persistencementioning

confidence: 99%

Operating system support for persistent and recoverable computations

et al. 1996

View full text Add to dashboard Cite

O PERATING systems manage a computer's resources, maintain its permanent data, and provide an efficient environment for the execution of user programs. Users expect an operating system to provide a certain level of resilience to failure and facilities for recovering from failure with minimal interruption of computations and minimal loss of data.In conventional operating systems, these tasks are centered around the file system as the repository of permanent data and virtual memory as the execution environment. Persistent systems offer an alternative view in which the lifetime of data is separated from the access mechanism. In a persistent system, all data, regardless of its lifetime, is created and manipulated in a uniform manner.When persistence is included as the basic abstraction of an operating system, many of the inadequacies of existing operating systems are eliminated and the tasks of an application J o h n R o s e n b e r g , A l a n D e a r l e , D a v i d H u l s e , A n d e r s L i n d s t r ö m , a n d S t e p h e n N o r r i s OPERATING SYSTEM SUPPORT FOR PERSISTANTand RECOVERABLE COMPUTATIONS Guaranteeing data recovery and consistency, the authors' experimental Grasshopper persistent operating system simplifies application development and encourages construction of integrated systems.

show abstract

“…The first is to restrict code generation to certain trusted programs such as compilers. This is the approach taken in systems such as Napier88 [18]. An alternative scheme, adopted in MONADS, is to support a higher level architecture which provides mechanisms which can be used by compilers to implement various protection protocols, but which themselves guarantee that the ability to generate code cannot violate the security of the system.…”

Section: Higher Level Architecturementioning

confidence: 99%

Stability in a Persistent Store Based on a Large Virtual Memory

Rosenberg

Henskens

Brown

et al. 1990

Workshops in Computing

View full text Add to dashboard Cite

Persistent systems support mechanisms which allow programs to create and manipulate arbitrary data structures which outlive the execution of the program which created them. A persistent store supports mechanisms for the storage and retrieval of objects in a uniform manner regardless of their lifetime. Since all data of the system is in this repository it is important that it always be in a consistent state. This property is called integrity. The integrity of the persistent store depends in part on the store being resilient to failures. That is, when an error occurs the store can recover to a previously recorded consistent state. The mechanism for recording this state and performing recovery is called stability. This paper considers an implementation of a persistent store based on a large virtual memory and shows how stability is achieved.

show abstract

The Napier Type System

Cited by 20 publications

References 15 publications

Exploiting Persistence in Build Management

Exploiting Persistence in Build Management

Operating system support for persistent and recoverable computations

Stability in a Persistent Store Based on a Large Virtual Memory

Contact Info

Product

Resources

About