Re: [pdf-devel] Fsys read/write return value.

[gerel]

 > Date: Thu, 14 May 2009 22:24:31 -0400
 > From: Michael Gold <address@hidden>
 > Content-Disposition: inline
 > 
 > 
 > --fdj2RfSjLxBAspz7
 > Content-Type: text/plain; charset=us-ascii
 > Content-Disposition: inline
 > Content-Transfer-Encoding: quoted-printable
 > 
 > On Thu, May 14, 2009 at 23:00:50 -0300, gerel wrote:
 > =2E..
 > > I suggest getting rid of the ELEM_SIZE+ELEM_COUNT variables.  And, if a b=
 > igger
 > > than 1 octet should be read for buffering issues (fread/fwrite), that
 > > should be managed by the implementation and not published by the API.
 > >=20
 > > OTOH, I'd add a pdf_status_t variable either as an output parameter,
 > > or as a return value (and pass a pointer for returning the written/read s=
 > ize).
 > > We need a status flag.
 > 
 > Just copy the pdf_stm_read prototype, which has all the necessary
 > parameters:
 >   pdf_status_t pdf_fsys_file_read( pdf_fsys_file_t file,
 >                                    pdf_char_t *buf,
 >                                    pdf_size_t bytes,
 >                                    pdf_size_t *read_bytes )
 > 

Sure Michael, I'll send a patch for both read/write as soon as we all agree on
this.

cheers,

-gerel