Hi Cirilo.
What's the latest news on error reporting within the libs?
We included some functions in `pdf-error.[ch]' that provide support
for tracing.
The GNU docs recommend something like
fprintf(stderr, __FILE__ ": %d: something went wrong: %s\n",
__LINE__, cause);
We can output that data using the pdf-error.c functions.
If you could indicate the position within the FILE (not within the
stream), that may be useful for debugging the read/write routines
later on because you can use a hex editor to inspect the file.
That is a quite good idea.
--
Jose E. Marchesi <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
GNU Spain http://es.gnu.org
GNU Project http://www.gnu.org
