Re: Ada.strings.bounded problems?

[mab@wdl1.wdl.loral.com (Mark A Biggar)]

In article <D3Bqzw.D12@inmet.camb.inmet.com> brennan@panther.warm.inmet.com (William Brennan) writes:
>Please, what are "passive tasks"? (Non-periodic ones?)
>Why is it important for the optimizer to recognize them?

A "passive task" is one that does nothing significant outside of any
of its accept statements; such a task doesn't really need a separate
thread of control as it can do all its work piggy backed on the thread of
control of any task that calls one of its entries.  A simple example is:

task foo is 
    entry a;
    entry b;
end foo;

task body foo is
begin
    loop
        select
            accept a do
                -- do task operation a
            end a;
        or
            accept b do
                -- do task operation b
            end b;
        end select;
    end loop;
end foo;

The simple buffer tasks often required by the Ada tasking model a usually
passive tasks.

Recognizing that a task is passive can greatly reduce the amount of code 
necessary to be generated for it and also reduces the run time burden on
the tasking run time system.  That this optimization can be so useful
is one of the reasons that "protected objects" were added to the Ada95
specification.

--
Mark Biggar
mab@wdl.loral.com