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,
	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: 
 g2news2.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Why no socket package in the standard ?
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: <op.vvyoslycule2fv@douda-yannick>
 <872169864327910446.796089rmhost.bauhaus-maps.arcor.de@news.arcor.de>
 <9cb23235-8824-43f4-92aa-d2e8d10e7d8c@ct4g2000vbb.googlegroups.com>
 <1jue77mrlbkor$.1iuz25va18fvm$.dlg@40tude.net>
 <df294cc9-2e1d-4014-ad7e-8d6a0fdc3a82@28g2000yqu.googlegroups.com>
Date: Wed, 25 May 2011 11:14:10 +0200
Message-ID: <1sg3bjezic084.idxvmhddw1hd$.dlg@40tude.net>
NNTP-Posting-Date: 25 May 2011 11:14:10 CEST
NNTP-Posting-Host: 733f4355.newsspool1.arcor-online.net
X-Trace: 
 DXC=WJR;<0M:26]U6b:FjPaGjQic==]BZ:af^4Fo<]lROoRQ<`=YMgDjhgRQ30`UN=@g4[[6LHn;2LCV^7enW;^6ZC`T\`mfM[68DCSLJFj?g^e26[
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:20434
Date: 2011-05-25T11:14:10+02:00
List-Id: <comp.lang.ada>

On Tue, 24 May 2011 14:22:42 -0700 (PDT), Maciej Sobczak wrote:

> On 24 Maj, 09:25, "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de>
> wrote:
> 
>>> In the language? Probably none, as this does not belong to the
>>> language.
>>
>> That is an interesting question. Actually sockets could belong to the
>> language. Consider for example the select statement containing alternatives
>> of a socket's select.
> 
> Still, they (sockets) don't have to be part of the language to be
> select-ready. It is enough to make them protected objects with
> appropriate entries.

1. We need to be able to cancel connect/accept/send/receive from an AST or
timed entry call.

2. We should never do any I/O related stuff on the context of a protected
action.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de