2009/12/23 Andrew Bennetts <email address hidden>:
> Yeah. Or at least for every case where errno might be EINTR or
> otherwise caused by the arrival of a signal... I'm not sure if there are
> any?. A common function sounds like a good idea.
There are some functions classified as 'fast' (if that's the right
word) that will always finish without being interrupted. time(2) is
an obvious example. However it's harmless to check and probably
simpler to just do it everywhere.
2009/12/23 Andrew Bennetts <email address hidden>:
> Yeah. Or at least for every case where errno might be EINTR or
> otherwise caused by the arrival of a signal... I'm not sure if there are
> any?. A common function sounds like a good idea.
There are some functions classified as 'fast' (if that's the right
word) that will always finish without being interrupted. time(2) is
an obvious example. However it's harmless to check and probably
simpler to just do it everywhere.
-- launchpad. net/~mbp/>
Martin <http://