Re: Why no socket package in the standard ?

[anon@att.net]

Ada was designed to be "Portable" and "System Independent and Secure" 
which means that most system library packages such as Sockets are not 
apart of the main Ada language. 

To the Ada programmer, Ada removes the concerns of how it communicates 
with other components, like from server task communication to and from a 
client task. No, programmer needs to know if the system is using 
system-wide stacks or queues or if the communication is via a parallel, 
serial or network port. This may explain why "Annex E. Distributed Systems" 
is thin in it scope. The main problem is that since Ada 95 the design has 
been more toward "oops" programming than modifying the run-time system to 
keep up with new technology.

Plus, there is no language that contains Sockets as apart of it standard 
library.  C, C++, Java, Fortran, etc. have no references to Sockets in 
their standard language.  Sockets is an add on system library package to 
all languages and that includes Ada.  For Ada, the main problem here is 
that most Ada programmers spend their time writing application and not 
"Add On" libraries for Ada. They just bind what they need instead of 
building the complete library package for future projects.


In <op.vvyoslycule2fv@douda-yannick>, =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= writes:
>Hello one again,
>
>According to http://www.ibm.com/developerworks/linux/library/l-sockpit/
>> First introduced into the 4.2 BSD UNIX=C2=AE operating system,
>> the Sockets API is now a standard feature of any operating system.In  =
>
>> fact, it's hard to find a modern language that doesn'tsupport the  =
>
>> Sockets API.
>
>This may help Ada (and be useful too) to add sockets in standard package=
>s.
>
>There is AdaSockets, http://www.rfc1149.net/devel/adasockets.html
>which has cool licensing terms:
>> This library lets you use BSD sockets from Ada (TCP, UDP and multicast=
>).
>> It is released under the GNAT Modified General Public License, which  =
>
>> means
>> that you can freely AdaSockets in a proprietary application without  =
>
>> having
>> it contaminate your code.
>
>Nice, but still not part of the standard, and I cannot see a reason why,=
>  =
>
>such a fundamental thing, at least as fundamental as file access and  =
>
>standard I/O streams are, is not part of the standard packages. May be a=
>  =
>
>candidate for an optional annex at least ? Already discussed or not ?
>
>Sorry for any inconvenience if I ever missed something there (this  =
>
>question seems so much basic I can't avoid feeling I've missed something=
>).
>
>
>-- =
>
>Si les chats miaulent et font autant de vocalises bizarres, c=E2=80=99es=
>t pas pour  =
>
>les chiens.
>=E2=80=9C c++; /* this makes c bigger but returns the old value */ =E2=80=
>=9D [Anonymous]