Hi,

Ted Dennison wrote:

> In article <3A7A84C3.2486A6CF@avitech.de>,
>   Juergen Fischer <juergen.fischer@avitech.de> wrote:
>
> > but from other C programs we know that it doesn't take much CPU load.
> > So we suppose that the CPU load is caused by
> > Ada tasking in combination with the XtAppMainLoop.
>
> That doesn't make much sense to me. Furthermore, it sounds a lot the the
> "it must be Ada's fault" knee-jerk reactions I always get when I mention
> Ada in the context of a problem to OS library people.

Sorry about that, I am only looking for a solution and it was not my
intention
to polemize against Ada.

>
>
> But in any event, it should be trivial to check this assumption. Just
> replace your Ada "main" with a C "main", and see what happens. I'll bet
> you a virtual beer that you get the exact same behavior. :-)

I have reduced the Ada "main" to the start of the XtAppMainLoop. With all
other tasks
switched off  there is no CPU load (same behaviour as in a C program). With
all other
tasks switched on but XtAppMainLoop not started the process does not consume
CPU,
either. Only the combination of XtAppMainLoop and the other application
tasks leads to
CPU load although the application, after initialization, is in a wait state.

I compiled the Ada Sources with ObjectAda 7.1.2. The OS is HP_UX 10.20.

Juergen

>
>
> > Who has already used XtAppMainLoop within an Ada program?
>
> I have. Did it on the old SunOS using a VADS compiler, and once on the
> Harris Nighthawk. The only real problem I can remember was that we had
> to make sure that only the XtAppMainLoop task made any X calls (and I
> think there are X bindings available that remove that restriction).

In my application no other task makes any X calls.

>
>
> --
> T.E.D.
>
> http://www.telepath.com/~dennison/Ted/TED.html
>
> Sent via Deja.com
> http://www.deja.com/