Re: [pdf-devel] Streams solution proposal

[jemarch]

   > That backend is really useful for testing purposes, but the streams
   > should use the fsys implementation to access files stored in
   > filesystems (we will be able to test the streams operating through a
   > fsys as soon as we get the default filesystem completed). Anyway we
   > can integrate it in the library code.
   >

   Yep, It was intented to be used for testing purposes, not as a
   substitute of the fsys_file be.

Well, we can add the code anyway without documenting the backend in
the reference manual.

   > Some of your improvements on pdf-filter.c are quite interesting,
   > especially for testing purposes.
   > 
   > So what do you think about to integrate the c-file backend and the
   > improvements on pdf-filter to work with the current implementation of
   > streams?

   Ok, I'll do it this evening.

Superb. Many thanks.

   I can't promise it but if I have time I will try to prepare some
   automatic tests. The problem with the CHECK interface is that it is
   easier to test the filters interfacing with pdf-filter from
   bash. Anyway, I'll try to look CHECK more deeply and find out the
   best way to build tests for the filters.

I am not sure about the convenience to use the pdf_filter utility to
make unit tests. The unit tests for pdf_stm_read, pdf_stm_write, etc
can load the data from files to make the comparisons.