Main Page Namespace List Class Hierarchy Alphabetical List Compound List File List Namespace Members Compound Members File Members Related Pages

# RtecBase Namespace Reference

Define types shared by the real-time scheduling and event services. More...

## Compounds
struct | RtecBase::Dependency_Info
## Typedefs
typedef long | handle_t
| Provide a fast, low-footprint identifier for RT_Infos. More...
typedef long | OS_Priority
| Helper typedef to define the OS priority.
typedef long | Preemption_Priority_t
| Helper typedef to define the OS-independent priority.
typedef long | Preemption_Subpriority_t
| Helper typedef to define the OS-independent sub-priority.
## Enumerations
enum | Dependency_Type_t { ONE_WAY_CALL, TWO_WAY_CALL }
| Specify one-way or two-way call. More...

## Detailed Description

Define types shared by the real-time scheduling and event services.

These types are defined in a separate module to decouple the real-time event services from the scheduling service interface (and implementation!)

## Typedef Documentation

typedef long RtecBase::OS_Priority

| Helper typedef to define the OS priority.

typedef long RtecBase::Preemption_Priority_t

| Helper typedef to define the OS-independent priority.

typedef long RtecBase::Preemption_Subpriority_t

| Helper typedef to define the OS-independent sub-priority.

typedef long RtecBase::handle_t

| Provide a fast, low-footprint identifier for RT_Infos. The Event and Scheduling Service need to communicate information about RT_Infos (descriptions about the scheduling properties of a simple operation). On a centralized application one would use pointers for such a task, but obviously that does not work on a distributed system. It is tempting to use object references to identify each RT_Info, but that does not work either: first the *contents* of the RT_Info must be transmitted between applications, and object references are not good identifiers (due to the semantics of _is_equivalent()) The handle_t type is used to generate unique identifiers on the scheduling service, the Event Service can then refer to any RT_Info using either their name or the quicker handle_t.

## Enumeration Type Documentation

enum RtecBase::Dependency_Type_t

  | Specify one-way or two-way call. Enumeration values:
  ONE_WAY_CALL |
  TWO_WAY_CALL |