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=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham 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,UTF8 Path: g2news1.google.com!news4.google.com!feeder.news-service.com!feeder.news-service.com!94.75.214.39.MISMATCH!aioe.org!.POSTED!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: Why no socket package in the standard ? Date: Wed, 25 May 2011 02:34:16 +0200 Organization: Ada @ Home Message-ID: References: <872169864327910446.796089rmhost.bauhaus-maps.arcor.de@news.arcor.de> <4ddc33be$0$6547$9b4e6d93@newsspool4.arcor-online.net> <4ddc451a$0$6546$9b4e6d93@newsspool4.arcor-online.net> NNTP-Posting-Host: eKwzOZEoYNmUIKtjz8NWow.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/11.01 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Xref: g2news1.google.com comp.lang.ada:19443 Date: 2011-05-25T02:34:16+02:00 List-Id: Le Wed, 25 May 2011 01:54:02 +0200, Georg Bauhaus = a =C3=A9crit: > An abstraction like "network data communication" which > would be similar to Sequential File. Whichever way the > latter happens to be available in the external environment, > you can open the file, read or write items, close it, > etc. IPC have unavoidable properties, which are as real as physics is, and = which cannot be expressed in terms of file access. File access is somewh= at = pure and simpler than IPC, and is just a particular case of IPC, which = (the latter) is wider. > http://www.unicode.org/history/earlyyears.html > > Specifically, you can see how requirements were weighed > and how the process didn't just revolve around just one > precendent. Will read this later (I interested in Unicode since very long). Any way,= = Unicode code points still match ISO 8859-1 (which does not require = mapping). > "But all of a sudden, we could see the light go on in both > of our faces: we had assumed that the standard ABC was a XYZ > standard. We were so, so wrong. You needed WYZX to represent > even the most common N. Worse yet, some P could be both G > and H. We weren't in Kansas anymore!" Oops, will have to read this again and again before I am sure I've = understood (where does this quote originates ? a novel ?). > I'm guessing that the same is going to happen if the Ada > standard were to quickly adopt BSD Sockets. Stooooop. I agreed for a better abstraction multiple since your last replies ;) >>> - it seems completely sufficient to agree, outside the standard, >>> on an API that can be used with any Ada compiler. No >>> standardization is needed at all. >> OK. Let say it is not required, so "not" may be an option. > > Because a language standard is about things more general > than a specific networking library. You said this after you though I wanted BSD sockets, strictly. But that = is = not, I want, not BSD sockets, but the functionalities BSD sockets = provides. And these are not available through the file nor the stream = interface of actual Ada. -- = 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]