Ken Hornstein <[email protected]> writes:
>> inc.c contains two occurrences of this:
>>
>> fseek (fp, 0L, SEEK_CUR);
>> pos = ftell (fp);
>>
>> Is that fseek() ever necessary?
> Hrm. According to the man page, a successful call to fseek() clears the
> eof indicator and undoes any ungetc() call. Not sure we want the latter,
> but maybe they're trying to do the former? fp is opened using
> fdopen(.., "w+"), so I could see it being at EOF.
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?
regards, tom lane
_______________________________________________
Nmh-workers mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/nmh-workers
