Hi gerel.
> Gerel, what do you think about this? We would of course loose the
> benefits of the opaque pointers in this case, but 'pdf_obj_equal_p'
> throwing PDF_ENOMEM sounds quite weird, and I think that we could make an
> exception and publish the iterator structure.
Well, before going further, I think the design of the list module
is ok as it is now. We can write any predicate procedure on top of
any module and not for that reason the module is to blame on status
codes. We have to deal with status codes.
[...]
That said, I'll modify the API and implementation of the list
module if you still believe it is the correct path.
Sorry, I got confused and read 'pdf_list_equal_p'. Never mind about
'pdf_obj_equal_p' :)
--
Jose E. Marchesi <jema...@gnu.org>
http://www.jemarch.net
GNU Project http://www.gnu.org
