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

Aditya wrote:

> The application starts and opens(creates) a file, and waits for an
> input to be written to the file.
> 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).

At this point, you've thoroughly left the region of topicality of this 
newsgroup.  The C programming language doesn't know about multiple 
terminals, multiple processes, or other such things.

> 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.

Your assumption that the file is non-existant is wrong.  To find out 
why, you'll have to consult platform-specific documentation.
-- 
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.