Re: Behavior of fwrite(), fseek(), fflush() if the file gets deleted after being opened.

On Apr 1, 10:16=A0am, Aditya <adityagupta...@[EMAIL PROTECTED]
> wrote:
> I delete the file using rm -f <filename> as soon as the application
> starts before I give it an input to the application(just to clarify, I
> delete it from a different terminal, without stopping the application
> to wait for an input).
> Now I give the input and debug through the application, I find that
> the fseek(), fwrite(), fflush() calls in the application for writing
> to the file do not throw error even though the file is not existant.

This is just the way Unix systems work. A file can be removed while
it's still open, and it'll stick around until it's closed by every
process that has it oipen. Other systems work differently - on
Windows, for example, deleting an oipen file will fail.
-- 
comp.lang.c.moderated - moderation address: clcm@[EMAIL PROTECTED]
 -- you must
have an appropriate newsgroups line in your header for your mail to be
seen,
or the newsgroup name in square brackets in the subject line.  Sorry.