Re: problems with interfacing c

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Fri, 21 Jan 2011 00:03:22 +0100, Dmitry A. Kazakov  
<mailbox@dmitry-kazakov.de> a écrit:
>> Some body do, for some kind of raw IO. Just that this may be more  
>> oftenly
>> something like
>>     Character'Read (Standard_Input), C);
>
> That the point, when reading characters that suggests some character  
> stream
> oriented protocol. Dealing with such protocols one would never read 100K  
> in
> one chunk. Because if the client does something wrong that would deadlock
> forever.
This could block for a single character as much. The only way to not block  
would be either to test before read; this implies to read an item at a  
time, before the condition must be checked before each item is read (so a  
loop), or else indeed to use asynchronous IO as you suggested later. With  
the latter choice, buffered IO is OK. You may use Overlapped IO in  
Windows, alternatively, there are nonblocking socket IO available (returns  
WSAEWOULDBLOCK error if a read access would block). Don't know about POSIX  
(oops).

(I feel to remember there was a talk here about buffered IO, I cannot  
remember the thread's title)

-- 
Si les chats miaulent et font autant de vocalises bizarres, c’est pas pour  
les chiens.

“I am fluent in ASCII” [Warren 2010]