2010.02.26 08:11 "[Tiff] Patch for tif_unix.c", by Eric Doenges
- 2010.02.26 14:30 "Re: [Tiff] Patch for tif_unix.c", by Edward Lam
-
2010.02.26 17:05 "Re: [Tiff] Patch for tif_unix.c", by Bob Friesenhahn
- 2010.02.26 17:43 "Re: [Tiff] Patch for tif_unix.c", by Edward Lam
-
2010.03.02 08:14 "Re: [Tiff] Patch for tif_unix.c", by Eric Doenges
- 2010.03.02 14:11 "Re: [Tiff] Patch for tif_unix.c", by Toby Thain
- 2010.03.02 14:21 "Re: [Tiff] Patch for tif_unix.c", by Edward Lam
2010.03.02 14:11 "Re: [Tiff] Patch for tif_unix.c", by Toby Thain
On 2-Mar-10, at 3:14 AM, Eric Doenges wrote:
- What is the correct response to receiving EINTR (i.e. being interrupted before any data is read/written) ? Should the IO operation simply be retried in _tiffReadProc/_tiffWriteProc,
That would seem to be unhelpful, as the external cause seems to be intended to stop processing (a partial read/write is unimportant in that case). That would be the means to escape the loop?
Unless I'm missing something.
--Toby
- or should the caller handle it ?