Re: Tasking problem (delay)

[Gerd <GerdM.O@t-online.de>]

On 15 Aug., 20:32, "Jeffrey R. Carter"
<spam.jrcarter....@acm.nospam.org> wrote:
>
> The expression in the delay statement (in this case "WD_Delay") is
> evaluated once upon reaching the select statement. So this will wait for
> a call to Data, or for the value of WD_Delay at the time the select
> statement was reached, whichever comes 1st.
>
> Using unprotected shared variables is not a good idea anyway. I'd
> suggest something more like:

Thanks, you've pointed me into the right direction. I changed my code
such, that the delaytime is no longer a global variable (which in fact
was not good coding).

task worker is
  entry Data(...);
  entry set_delay_time(dt : Duration); -- inserted
end worker;


task body startup is
begin
  ...
-- WD_Delay := 1.0;
  worker.set_delay_time (1.0);
 ...
end startup;


task body worker is
  WD_Timeout : Duration := 1000.0;
begin
  loop
    select
       accept Data (...);
   or
      accept set_selay_time (dt : Duration)
      do
        WD_Timeout := dt;
      end;
   or
     delay WD_Timeout;
     trigger_WD;
    end select;
  end loop;
end worker;


Would this be a good solution for my problem or are there any other
traps?


Gerd