Re: RTT::FileDescriptorActivity and hasError()

S Roderick <[email protected]> Wed, 17 Sep 2014 08:08:20 -0400
Newsgroups gmane.science.robotics.orocos.devel
Message-ID <[email protected]>
On Sep 05, 2014, at 04:14, Matthias Goldhoorn <[email protected]> wrote:

> i just discovered that the RTT::FileDescriptorActivity::hasError() 
> function returns true if a file descriptor read was interrupted by a 
> System interrupt.
> 
> (errno -4), this is afaik not a error in general, the hasError() 
> function should only return critical errors, from my point of view if a 
> read is too often interrupted the timeout should catch. I would like 
> therefore to modify the function that errnor -4 is ignored.
> 
> Thougts?

Where errno-4 == EINTR, I think that this should be configurable. Not all applications will want to ignore this, while some will want to ignore it. I don’t think we can make a global policy decision here.

YMMV
S

-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev