Welcome to the NetCologne GmbH open source mirroring service!

This machine mirrors various open-source projects. 20 Gbit/s uplink.

If there are any issues or you want another project mirrored, please contact mirror-service -=AT=- netcologne DOT de !

General

General

Name

activity --  Processing control over all levels of Swarm execution

Description

The activity library is responsible for scheduling actions to occur within a simulated world, and for making these actions actually happen at the right time in the right order. It provides the foundation of dynamic, object-oriented simulation within Swarm.

Actions consist of messages to objects, calls to functions, or groups of actions in some defined order. The activity library guarantees that all these actions, and the state changes they produce, occur at predictable points in time. Time is defined by the relative order of actions, and may also be indexed by the discrete values of a world clock.

Macros

Functions

Typedefs

Globals

id <Symbol> Initialized

Values returned by getStatus.

id <Symbol> Running

Values returned by getStatus.

id <Symbol> Holding

Values returned by getStatus.

id <Symbol> Released

Values returned by getStatus.

id <Symbol> Stopped

Values returned by getStatus.

id <Symbol> Terminated

Values returned by getStatus.

id <Symbol> Completed

Values returned by getStatus.

id <Symbol> Concurrent

values for DefaultOrder

id <Symbol> Sequential

values for DefaultOrder

id <Symbol> Randomized

values for DefaultOrder

id <Symbol> HoldStart

Values returned by getHoldType.

id <Symbol> HoldEnd

Values returned by getHoldType.

id _activity_current

Internal variable used by current context macros.

id <Error> InvalidSwarmZone

Error issued when an internal zone is expected, but absent.

id _activity_zone

_activity_zone -- zone in which activity objects created

BOOL (*) (id) _activity_trace

trace function for activity execution global variable for function to be called on every change in the activity tree Note: support for any specific form of this trace facility is not guaranteed in future versions. Some form of trace facility will remain for debug purposes, however, at least until a full form of event history logging has been implemented as an integral part of the Activity type.