Constructs an active scheduler.

After construction, the scheduler should be installed.

CActiveScheduler::Install

Frees resources prior to destruction.

Specifically, it removes all active objects from the active scheduler's list of active objects.

An active scheduler should only be destroyed when the top-level call to Start() has returned.

CActiveScheduler::Start CActiveScheduler::Stop

Adds the specified active object to the current active scheduler.

An active object can be removed from an active scheduler either by destroying the active object or by using its Deque() member function.

Gets a pointer to the currently installed active scheduler.

The inner active scheduler loop. This repeatedly waits for a signal and then dispatches the highest priority ready active object. The loop terminates either if one of the RunLs stops the current active scheduler level or leaves.

Handles the result of a leave occurring in an active object s RunL() function.

An active scheduler always invokes an active object s RunL() function under a trap harness.

The default implementation must be replaced.

Any cleanup relevant to the possible causes of leaving should be performed. If Stop() or Halt() is called from within this function, the current wait loop terminates. This may be an appropriate response to catastrophic error conditions.

Extension function

Unilaterally terminates the current scheduler loop.

This causes the current scheduler loop to stop, whether it was started using CActiveSchedulerWait::Start() or CActiveScheduler::Start() . It can also trigger a leave from Start() if an exit code is provided. If the current level has already been stopped, then this still records the exit code.

Installs the specified active scheduler as the current active scheduler.

The installed active scheduler now handles events for this thread.

The current active scheduler can be uninstalled by passing a NULL pointer.

Use the StackDepth() function instead.

Gets the scheduler's level of nestedness.

StackDepth()

Dummy EXPORT for Binary Compatibility reasons. This method is never called.

Dummy EXPORT for Binary Compatibility reasons. This method is never called.

Allows the current active scheduler to be replaced, while retaining its active objects.

Dummy EXPORT for Binary Compatibility reasons.

Dummy EXPORT for Binary Compatibility reasons.

Start dispatching request completions.

Stop when aLoop becomes 'Inactive'

This version uses the original implementation of TRAP/Leave.

Causes the RunL() function of at most one pending active object of priority aMinimumPriority or greater to be run.

Gets the current number of nested wait loops.

Starts a new wait loop under the control of the current active scheduler.

At least one active object, with an outstanding request, must be added to the scheduler before the wait loop is started, otherwise no events will occur and the thread will hang, or any events that do occur will be counted as stray signals, raising a panic.

While Start() is executing, user code runs only:

1. in the RunL() function of active objects known to the current active scheduler

2. in the RunError() function of an active object that leaves from its RunL()

3. in the current active scheduler s Error() function, if an active object s RunError() returns an error code.

Start() returns only when a corresponding Stop() or Halt() is issued.

Although this can be used to start a nested wait loop, this API is deprecated for that specific functionality, and a CActiveSchedulerWait object should be used instead.

(Note that a nested wait loop is used when the handling of a completed event in an active object requires the processing of further events from the other active objects before it can complete. This is a form of modal processing.)

Start a new nesting level

Stops the wait loop started by the most recent call to Start() .

Typically, this is called by the RunL() of one of the scheduler s active objects. When this RunL() finishes, the scheduler s wait loop terminates, i.e. it does not wait for the completion of the next request.

It will not stop a wait loop started by a call to CActiveSchedulerWait::Start() .

Stop() may also be called from Error() .

Note that stopping a nested wait loop is deprecated using this functionality, use a CActiveSchedulerWait object instead.

CActiveSchedulerWait::Start CActive::RunL CActiveSchedulerWait::Error CActiveSchedulerWait::AsyncStop

Wait for an asynchronous request to complete.

The default implementation just calls User::WaitForAnyRequest() .

Derived classes can replace this. Typically, this would be done to implement code for maintaining an outstanding request; this would be followed by a call to User::WaitForAnyRequest() .

User::WaitForAnyRequest