Re: Blocking protected ops (was: Tasks and C/C++ code)

["David Botton" <dbotton@hotmail.com>]

After all the discussion on this issue, I am not sure how to implement a
call to gethosbyname any more.

Would some one post a correct implementation of this and if one can wrap
gethostbyname in to a protected type so it can be called by multiple task
instances even if it (gethostbyname) is not thread safe.

Thanks,
David Botton

Simon Wright wrote in message ...
>eachus@spectre.mitre.org (Robert I. Eachus) writes:
>
>> In article <365BE117.59209A5@elca-matrix.ch> Mats Weber
<Mats.Weber@elca-matrix.ch> writes:
>>
>>  > I don't think so. Look closely at 9.5.1(16&18). Subprograms imported
>>  > with pragma Import are not covered.
>>
>>    Eighteen only says that language-defined subprograms are not
>> potentially blocking unless the RM says otherwise.  Language-defined
>> here is a technical term applying to subprograms defined by the
>> Reference Manual.  Sixteen is the key here.  Within Ada, the RM can
>> define what is a potentially blocking subprogram, outside the
>> programmer has to figure it out for himself, which is why this is a
>> bounded error.
>
>I for one understood the language of 9.5.8 as meaning that _only_ the
>operations stated in 9-16 are 'potentially blocking', ie the list is a
>definition of what it is to be 'potentially blocking' and hence
>subject to possible checking by the runtime.
>
>There must be a difference between bad design and illegal design!