Re: [pdf-devel] FS module, file size and free space with different interface

[William Demchick]

> going - with a crude little utility to test it out.

Testing has been the hardest problem for me, so I am glad you have some ideas.

> There is quite a lot of work left to do, but this may be a good place
> to start depending
> on how much progress you've already made.

I have gotten most core functionality up and going (although, there is
still a lot of testing that should be performed).  I still have some
of the "higher level" functions left to implement, although it should
be fairly straight forward to use the core functionality to implement
them.

When I get a chance, I will take a peak at your implementation and see
what you've done.  It would be excellent if you could send me a quick
overview of where your at.  (Probably by private mail; no need to
bother everyone else for now.)

Thanks.

William Demchick


On Fri, Dec 10, 2010 at 3:53 PM, Scott Fohey <address@hidden> wrote:
> Hey William,
>
> I note that you've assigned yourself the HTTP filesystem implementation.
> I've been picking away at that for about a year. (Would swear that I assigned 
> it
> to myself some time ago, but cannot see any record of it in FlySpray)
>
> Attached is the merge directive of where I'm at. I have basic
> functionality up and
> going - with a crude little utility to test it out.
>
> There is quite a lot of work left to do, but this may be a good place
> to start depending
> on how much progress you've already made.
>
> Hey Jose,
>
> This isn't yet ready for prime-time, but since it's normally not
> built, would you consider
> applying it to the trunk so that William and I can both work at it?
> William: I'd take your
> input on this also...
>
>
> --Scott Fohey
>
>
> On Wed, Nov 10, 2010 at 4:39 AM, Jose E. Marchesi <address@hidden> wrote:
>>
>>    It seems like the change in return value to a pdf_size_t was based on
>>    an assumption that is no longer true:
>>
>>    > Yes, definitely. Since pdf_fsys_file_get_size operates in a
>>    > pdf_fsys_file_t and not in a path we can expect that should not be no
>>    > error in the execution of the function.
>>
>> It is ok to me to get pdf_fsys_file_get_size to return a status value
>> again.  But in that case please don't forget to update the
>> documentation in the gnupdf.texi file.
>>
>> --
>> Jose E. Marchesi   address@hidden
>> GNU Project         http://www.gnu.org
>>
>



-- 
Please read <http://www.fsf.org/campaigns/acta/> and
<http://bit.ly/dnrkcu> and <http://faces-against-acta.net/en/acta>...
then take action!