This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Intended semantics for syscalls function _read?


On 11/21/2016 04:06 PM, Eric Blake wrote:
> On 11/21/2016 07:16 AM, s.achterop@rug.nl wrote:
>>    Hello list,
>>
>> The documentation of this function does not describe how this function is to behave.
>> Is it blocking, or can it also be non-blocking.
>> What is the meaning of the return value? Or is it intentionally left ambiguous?
> 
> Your _read() function is supposed to behave similarly to the
> POSIX-defined read(2) function:
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/read.html

   Hello Eric,
thanks for the to the point answer.
Until now I interpreted the syscalls (wrongly) as some low level interface,
probably because I used it in that way in my embedded systems.
 Thanks again,
     Sietse



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]