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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5d05ccde5cefb836 X-Google-Attributes: gid103376,public From: Mats Weber Subject: Re: Tasks and C/C++ code. Date: 1998/11/23 Message-ID: <36599BE3.BA30555B@elca-matrix.ch>#1/1 X-Deja-AN: 414856567 Content-Transfer-Encoding: 7bit References: <364702E5.F6987321@hiwaay.net> <729ndu$jfo$1@nnrp1.dejanews.com> <72b35b$pll$1@nnrp1.dejanews.com> <87btm52jwl.fsf@zaphod.enst.fr> <3654746F.3C297E56@elca-matrix.ch> <87k90qunxl.fsf@zaphod.enst.fr> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: ELCA Matrix SA Mime-Version: 1.0 Reply-To: Mats.Weber@elca-matrix.ch Newsgroups: comp.lang.ada Date: 1998-11-23T00:00:00+00:00 List-Id: Samuel Tardieu wrote: > Mats> Why not ? If the C function is potentially blocking _and_ > Mats> non-reentrant (as is gethostbyname for example, which can take > Mats> some time), then it's the only option. > > 9.5.1 (8) During a protected action, it is a bounded error to invoke > an operation that is potentially blocking. > > I think that the spirit of protected operations is to be really short. OK, but the definition of "potentially blocking" does not include imported subprograms (RM 9.5.1(8-18)). So I guess this is undefined. But given the spirit of the definition, I agree that it would be better to put the call in a task body instead of in a protected body, in order not to be too close to the boundaries of the standard. Anyway I have seen gethostbyname protected by a protected object (I think it is in GLADE). So it does work.