[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pdf-devel] Missing stream backend error conditions.
From: |
Michael Gold |
Subject: |
Re: [pdf-devel] Missing stream backend error conditions. |
Date: |
Tue, 19 May 2009 02:23:06 -0400 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
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
signature.asc
Description: Digital signature
- [pdf-devel] Missing stream backend error conditions., gerel, 2009/05/18
- Re: [pdf-devel] Missing stream backend error conditions., Michael Gold, 2009/05/18
- Re: [pdf-devel] Missing stream backend error conditions., jemarch, 2009/05/19
- Re: [pdf-devel] Missing stream backend error conditions., gerel, 2009/05/19
- Re: [pdf-devel] Missing stream backend error conditions., Michael Gold, 2009/05/22
- Re: [pdf-devel] Missing stream backend error conditions., jemarch, 2009/05/25