An Implementation of Scoped Memory forReal - Time

Scoped Types and Aspects for Real-Time Java

Real-time systems are notoriously difficult to design and implement, and, as many real-time problems are safety-critical, their solutions must be reliable as well as efficient and correct. While higher-level programming models (such as the Real-Time Specification for Java) permit real-time programmers to use language features that most programmers take for granted (objects, type checking, dynam...

Cost Analysis for Real - time Java Scoped - memory Areas ∗

Java has recently joined C and C++ as a development platform for real-time and embedded applications. Java’s garbage collection, while generally a useful feature, can be problematic for these applications: garbage collection occurs at unpredictable times and its latency is typically unbounded. This can compromise necessary real-time guarantees. To overcome these limitations, the Real-Time for J...

Optimizing scoped and immortal memory management in real-time Java

On the Development of Dynamic Real-Time Applications in the RTSJ - A Model for Expressing Dynamic Memory Requirements

The Real-Time Specification for Java (RTSJ) introduces a memory model that includes immortal and scoped memory areas that are not subject to garbage collection latencies. Unfortunately, it is often argued that the RTSJ’s memory model is unwieldy and even insufficiently expressive for describing the memory dynamics of simple and commonly used structures and patterns. This paper takes the positio...

Implementing Optimized Distributed Data Sharing Using Scoped Behaviour and a Class Library

Sometimes, it is desirable to alter or optimize the behaviour of an object according to the needs of a specific portion of the source code (i.e., context), such as a particular loop or phase. One technique to support this form of optimization flexibility is a novel approach called scoped behaviour. Scoped behaviour allows the programmer to incrementally tune applications on a per-object and per...