Re: tasking with GNAT 3.14p on windows

[Bernd.Specht@gmx.com (Bernd Specht)]

"James S. Rogers" <jimmaureenrogers@worldnet.att.net> wrote in 
news:W4Oha.35749$ja4.2291095@bgtnsc05-news.ops.worldnet.att.net:

> "Jano" <nono@celes.unizar.es> wrote in message
> news:MPG.18f18ac32e4a300d9896c8@News.CIS.DFN.DE...
>> James S. Rogers dice...
>> > "Bernd Specht" <Bernd.Specht@gmx.com> wrote in message
>> > news:Xns934E8C5D49EFBerndSpechtgmxcom@62.153.159.134...
>> > > Hi,
>> > >
>> > > I tried an example from "Barnes, 18.8", but it didn't work as
>> > > expected. Any ideas? 
>> > >
>> > > with Text_IO; use Text_IO;
>> > >
>> > > procedure TaskTest is begin
>> > >   select
>> > >     delay 3.0;
>> > >     put_line ("aborted");
>> > >   then abort
>> > >     loop
>> > >       null; -- modified
>> > >     end loop;
>> > >   end select;
>> > > end TaskTest;
>> > >
>> (...)
>> > The null command will reliably take less than 3.0 seconds to complete.
>>
>> It's inside of a neverending loop.
> 
> And optimization will remove the loop, leaving a single null statement.

No.

1. If this would be true, then the program should terminate after a short 
time, but in fact it is still not terminated after a few hours. so it seem 
to "hang" inside the loop.


2. If this would be the  case it would be a serious compiler error. An 
endless loop must never be removed by compiler optimisation (it would be 
interessting to know the opinion of Robert Dewar).

I hope my code

loop
  if Get_Pressure > Upper_Limit
  then
    Open_Valve;
  elsif Get_Pressure < Lower_Limit
  then
    Close_Valve;
  end if;
end loop;


still executes, and was not only executed once due to compiler optimisation 
(I don't like to be blown up due to an compiler "feature").

> 
> Jim Rogers
> 
> 
>