Hi David.
Is there any reason to we have got the `pdf_fsys_create' procedure?
It is supposed do:
-- Function: pdf_fsys_t pdf_fsys_create (struct pdf_fsys_impl_s
IMPLEMENTATION)
Create and return a new filesystem variable that will use a given
implementation.
which copy the `pdf_fsys_impl_s' structure.
I think we could assume pdf_fsys_t is a pointer to pdf_fsys_impl_s
(rename pdf_fsys_impl_s to pdf_fsys_s), in order to the library can
provide PDF_FSYS_DISK, PDF_FSYS_HTTP, etc, to use as pdf_fsys_t
directly.
The rationale after the existence of that function, and also after the
existence of two different types pdf_fsys_t and pdf_fsys_impl_s, is
that pdf_fsys_t is intended to be opaque. We may want to expand its
definition to hold data not related to an specific implementation.
---
Jose E. Marchesi [email protected]
GNU Project http://www.gnu.org
