[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] fseek(fp, 0, SEEK_CUR)?
From: |
David Levine |
Subject: |
Re: [Nmh-workers] fseek(fp, 0, SEEK_CUR)? |
Date: |
Tue, 15 Jan 2013 20:51:31 -0500 |
Tom wrote:
> David Levine <address@hidden> writes:
> > 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?
>
> "Opened and read"? I thought you said w+ ...
I got the sequence wrong above. It is: open, lseek, read.
> If it is read/write, I seem to recall that fseek is
> advised when switching between read and write modes. This
> may just be protecting against bugs in ancient stdio
> libraries, but ...
OK, thanks for the explanation.
David
- [Nmh-workers] fseek(fp, 0, SEEK_CUR)?, David Levine, 2013/01/14
- Re: [Nmh-workers] fseek(fp, 0, SEEK_CUR)?, David Levine, 2013/01/14
- Re: [Nmh-workers] fseek(fp, 0, SEEK_CUR)?, David Levine, 2013/01/15
- Re: [Nmh-workers] fseek(fp, 0, SEEK_CUR)?,
David Levine <=