Re: [pdf-devel] I'm Back at last

[jemarch]

   > 3. For pdf_error I'm considering writing wrappers for those
   > functions available on lib/error.c and to write new ones for
   > gnupdf as needed. OTOH, I'm pretty new on the project to know
   > which error types should be added. I guess we should analyse
   > each module on each layer and decide from there, don't you ?

   Some observations from pdf_function.c:
   Error reporting from a leaf module tends to be cryptic for a 
   mere user. For example, a pdf function dictionary may miss a 
   required key, the dictionary data may be inconsistent in 
   various ways, a type 4 function definition may have a syntax 
   error in its sublangage, and so on. 

   There are errors at function call time,too.
   A PDF shading function may be called millions of times,
   reporting each error is probably not useful.
   I'd need some way to defer error reporting.
   What about a pdf dictionary as "error object" ?
   It might be passed freely, accreting context as it moves?

Would be good to have some global data structure able to stack errors
of several severities. 

Note also that base stream modules doesnt have access to pdf
dictionaries.

   BTW,  my copyright assignment is finished. I hope I'll find time 
   to write useful test functions real soon now.

Thanks.

--
José E. Marchesi  <address@hidden>

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