On Tue, May 19, 2009 at 00:43:56 -0300, gerel wrote:
>  >   - PDF_EBADFILE could be returned if a filter reads invalid data
> 
> That kind of error is handled as PDF_ERROR (as read in the doc ref.)

PDF_ERROR is also raised by the backend when an unknown error occurs; so
if pdf_stm_read returns PDF_ERROR, there's no way to tell whether it's
because of a corrupt file.

...
>  > Also, EINTR either has to be handled in the backend (by retrying the
>  > operation), or propagated upward.
> 
> I guess it should be handled by the backend, so we can keep the API simpler.

Agreed -- since there's already code to loop on short reads/writes,
looping on EINTR shouldn't be a problem.

-- Michael

Attachment: signature.asc
Description: Digital signature

Reply via email to