From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,80ae596d36288e8a X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!news.glorb.com!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeder.news-service.com!94.75.214.39.MISMATCH!aioe.org!.POSTED!not-for-mail From: anon@att.net Newsgroups: comp.lang.ada Subject: Re: Why no socket package in the standard ? Date: Tue, 24 May 2011 18:29:56 +0000 (UTC) Organization: Aioe.org NNTP Server Message-ID: References: Reply-To: anon@anon.org NNTP-Posting-Host: TC3+/U5V7RyaX56KGzVAgw.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: IBM NewsReader/2 2.0 Xref: g2news1.google.com comp.lang.ada:19412 Date: 2011-05-24T18:29:56+00:00 List-Id: 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 , =?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]