Re: [Nmh-workers] fseek(fp, 0, SEEK_CUR)?

[David Levine]

Tom wrote:

> If it's opened w+, maybe the point is to be sure the ftell
> reports the current EOF rather than wherever we last wrote
> ourselves.  Is the file in question likely to be
> concurrently extended by other processes?

I don't think so, it looks like that file has always been
protected by a lock.

After the file is opened and read, it's lseek'd.  Is (or
was) it necessary, or advised, to do an fseek between the
subsequent fdopen and ftell?

David