Re: Ada Annex E (Just curious :-)

[Robert Spooner <rls19@psu.edu>]

I made my own bindings to sockets routines before AdaSockets was
available, and at least for Unix (Solaris) and VxWorks I was able to put
all the operating system dependent information in a single package body
where I defined a few constants such as the mask size for Select.  It
should also work for VMS if you want to use sockets rather than the QIO
interface.  I haven't looked at Windows closely enough to comment on how
different the sockets interface is for it.

You can know what to do about network order for parameters by testing
the Bit_Order attribute of a type with default bit ordering, so that
shouldn't be a portability issue.

Bob

Frank wrote:
> 
> Hi!
> 
> I guess it some kind of CORBA that is the solution for this kind of problem
> then?
> 
> Frank
> 
> >
> > I haven't looked at ADEPT in a long time, so I can't speak to that.  I
> > have had success using the AdaSockets collection on the natively
> > compiled Ada side, and the Socket class on the Java side (actually
> > JGNAT).  One does have to worry about host vs network byte order, and
> > what I've gotten so far is probably horribly non-portable, but for now
> > anyway it's working.
> >

-- 
                            Robert L. Spooner
                     Registered Professional Engineer
                       Associate Research Engineer
                  Intelligent Control Systems Department

         Applied Research Laboratory        Phone: (814) 863-4120
         The Pennsylvania State University  FAX:   (814) 863-7841
         P. O. Box 30
         State College, PA 16804-0030       rls19@psu.edu