Re: [pdf-devel] Some guidance ?

[jemarch]

   > There are two tasks that should be done:
   >
   > a) To improve the existing testing framework in torture/ writting a
   >    minimal common infrastructure to write unit tests. To use an
   >    external test driver is ok as long as it is simple and gplv3
   >    compatible.
   >
   > b) We still lack a proper error management in the library. Would be
   >    quite useful someone to think about it.


   Ok, I prefer "b". I'm going to familiarize with code first (3 days
   maybe).

Thanks.

   So, what are your ideas on item "b" ?

Right now there are several "modules" implemented in the library: the
stram abstraction (pdf_stm*.[ch]), the PDF objects (pdf_obj.[ch]),
etc. 

We should implement a pdf_error.[ch] module providing an API to:

- Signal fatal errors, terminating the process in an error state
- Manipulate a global error state (structure). The global state may
  work ala errno, having several levels of error harmness. When a
  routine in a module find an error (a pdf function find invalid
  input, for example) it will fill the global error state structure
  and then return PDF_ERROR to the caller.
- more?

Please note the availability of the "error" gnulib module in lib/

-- 
Jose E. Marchesi  <address@hidden>
                  <address@hidden>

GNU Spain         http://es.gnu.org
GNU Project       http://www.gnu.org