Re: Neater entry point code

[mheaney@ni.net (Matthew Heaney)]

In article <34989E2A.93EF7271@dsto.defence.gov.au>, Mark Rutten
<Mark.Rutten@dsto.defence.gov.au> wrote:

>The code that I have at the moment looks like
>
>    while Execute'Count /= 0 loop
>
>      accept Execute( In_Msg: in Message_Typ ) do
>        Msg := In_Msg;
>      end Execute;
>
>      Add_Msg(Msg);
>
>    end loop;
>
>    Execute_Stuff;

Note that naming the in parameter "In_Msg" isn't necessary; just use an
expanded name:

task body My_Task_Type is

   Msg : Message_Typ;

begin
...
   accept Execute (Msg : in Message_Type) do
      My_Task_Type.Msg := Msg;
   end Execute;
...

As Ben pointed out, it sounds like you want a protected object in
conjunction with a task.

You should hardly ever use T'Count for a task type, because of the race
conditions; it's pretty much a worthless attribute.

If you're ever tempted to use T'Count, don't.

--------------------------------------------------------------------
Matthew Heaney
Software Development Consultant
<mailto:matthew_heaney@acm.org>
(818) 985-1271