Oberon || Library || Module Index || Search Engine || Definition || Module

Ulm's Oberon Library:
ConstantObjects

NAME

SYNOPSIS

PROCEDURE RegisterType(VAR type: Services.Type;
                       name, baseName: ARRAY OF CHAR);
PROCEDURE Init(object: PersistentObjects.Object;
               type: Services.Type;
               name: ARRAY OF CHAR);

DESCRIPTION

• are created during the initialization time of a module,
• remain constant,
• may be considered identical independent from the process context, and
• have their own type extension of PersistentObjects.

The idea is that instead of transferring the whole contents of a constant object by marshalling procedures a name is sufficient to identify the same object in another process. In addition, constant objects do not get cloned and keep therefore referential integrity as objects imported or exported by RemoteObjects.

RegisterType is to be called instead of PersistentObjects.RegisterType for types of constant objects. Note that type must be exclusively used as a type of constant objects in the sense of this module.

Init is to be called instead of PersistentObjects.Init for constant objects. Note that name should be qualified with the own module name to avoid name conflicts.

DIAGNOSTICS

Assertions fail if

• PersistentObjects.ReadInto is called for constant objects, or if
• PersistentObjects.Init was called instead of Init. This is detected by the interface procedures for PersistentObjects.

SEE ALSO

Loader

dynamic loading of modules

PersistentObjects

operations for persistent objects

Oberon || Library || Module Index || Search Engine || Definition || Module