Re: tasking with GNAT 3.14p on windows

["Chad R. Meiners" <crmeiners@hotmail.com>]

"Jano" <nono@celes.unizar.es> wrote in message
news:MPG.18f2a01651aa20aa9896cb@News.CIS.DFN.DE...
> trying to know the behavior with blocking I/O. In XP with -gnatP, you
> get indefinite wait for user input, but if more than 10 seconds has
> passed when you hit enter, you get also the "aborted" print.
>
> Is that expected behavior? Gnat docs say that polling implements calls
> in each loop iteration / function call. Should I assume that if you
> haven't loops / calls, abort will never work properly?

It seems like reasonable behavior.  System calls are not guaranteed to be
abortable.

> I feel nevertheless very unsafe using anything else than trivial tasks
> in NT. The priority system of NT messes things greatly out of
> real_time_class, and that, for example, is never pointed in Gnat docs
> (in my knowledge).

NT is not a real time operating system.  The task support on NT is not
broken; your understanding of Ada tasking is broken. ;)  It is very easy to
write system dependent tasking code.  I have written several robust
multi-tasking windows applications.  You just have to understand how to
implement your os calls so that they play well with tasking.

> Also, the faulty ceiling_priority model for protected objects is
> mentioned or not? I can't remember...

If you don't know then why are spreading FUD about tasking on NT?