BTW, distributing gnulib headers along with
pdf.h is also a bad idea, isn't it?
I don't see anything very problematic with distributing them.
So the public API shouldn't depend
on any data type coming from those headers.
That indeed may be troublesome -- you wouldn't want a PDF application
programmer to end up declaring gl_list variables.
Jose's approach, as I understand it, is to have a PDF-specific type
which is used by the application programmers as part of the gnupdf api.
That type is implemented using gl_list (and so gl_list.h is part of the
gnupdf distribution), but that is opaque to gnupdf programmers. That
seems like exactly the right approach to me, for whatever my humble
opinion may be worth ...
Best,
karl
