Re: Feasibility of using Ada in new development

["Randy Brukardt" <randy@rrsoftware.com>]

"Wojtek Narczynski" <wojtek@power.com.pl> wrote in message
news:5ad0dd8a.0409090226.154b7b11@posting.google.com...
> Randy,
>
> > It would actually be fairly easy to build a special I/O library that
could
> > put a task to sleep (no threads here - only Ada :-). Just replace the
> > implementation of Read and Write.
>
> Are all the runtime sources included with the compiler so that a third
> party could do it for themselves?

They're available, but under a separate support agreement.

> > Of course that wouldn't work for sockets, because sockets aren't I/O in
> > Windows.
>
> Well, right now I am interested only in sockets. There is a select
> call and also some nice looking WSA* (Windows Sockets 2 API) calls
> that could be tried. But, also, I'd prefer to have it working on unix.

As I recall, I tried three different organizations of the server. They all
seemed to be limited by some limit in the number of connections that Windows
would allow through a single port at one time (although that may have been a
limit of our network or of the software somewhere). I eventually decided
that there having more than 16(?) simultaneous HTTP commands was happening
rarely enough that it wasn't worth figuring out why we couldn't get beyond
it.

There really isn't anything specificly Windows about our design, and indeed,
we used to support compilers on various Unix targets. There hasn't been
enough interest (or time in the day!) to port those to Linux, but it
wouldn't be very hard to do.

 > Yesterday I managed to patch and build the current fsu threads library
> http://www.informatik.hu-berlin.de/~mueller/ftp/pub/PART/pthreads.tar.gz
> and gnat 3.15p runtime together, so now I have complete working
> sources of a cooperative, or at least could-be-cooperative, runtime.
> Seems like a good starting point, as you also noted.

Sounds good. Good luck.

                     Randy.