Re: GUI Design for Ada

["Andrew" <mysig@fast.net>]

I think you are correct. The code was running on NightHawk series computers.
Concurrent Comp. Corp. Ft. Lauderdale owns them now. We switched to
PowerHawks.

This by far is the most complex piece of s/w I've ever worked on. It has
five processes and it's growing.

-------------------------------------------------------------------
Andrew


Ted Dennison <dennison@telepath.com> wrote in message
news:7vkavj$4av$1@nnrp1.deja.com...
> In article <7vdbff$9k1$1@news5.fast.net>,
>   "Andrew" <mysig@fast.net> wrote:
> > Ted Dennison <dennison@telepath.com> wrote in message
> > > Out of curiosity, what OS are you using?
> >
> > PowerMAX OS
> ...
> > unfortunately, we use OS calls and have an enhanced Ada83 compiler.
>
> Hmmm. Is that Harris' old VADS-based compiler? It was a rather nice
> system. I particularly liked the way it spilt Ada tasks into separate
> processes and automaticly load-balanced them across the available CPUs.
> It handled the different process-spaces by putting task heaps and
> program stacks in shared memory sections. But you still had to be very
> careful with using non-Ada dynamicly allocted memory in tasks that
> didn't do the initial allocation. With some C code you can get around
> the problem by redefining "malloc" to call Ada's "new" operator. But
> that wouldn't help us for some C library calls, like X and Motif.
>
> Ada 83 had numerous deficiencies wrt. real-time programming. The worst
> was the lack of a "delay until" statement. That's why we didn't even
> consider Ada 83 solutions for the program I'm working on now.
>
> --
> T.E.D.
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.