Testing file deletion from under ostream object.

[James Vanns]

How would one go about testing for the deletion of a file that sits
under an o[f]stream object? I've tried is_open, good(), fail(), eof(),
bad() and catching exceptions - nothing! Aparently the << operator
still succeeds which I guess is because it's still writing to the
buffer (but even flush() doesn't fail). If an external program (such as
rm or del) deletes the physical file - how can I catch this in the
program? In a relatively elegant, non-hacky way!?

Regards,

Jim Vanns

 

[Victor Bazarov]

[...] If an external program (such
as rm or del) deletes the physical file - how can I catch this in the
program? In a relatively elegant, non-hacky way!?

There are no means for that in the language. C++ assumes a _single_thread_
_single_process_ execution environment for its definitions. Whatever your
OS allows you to do and the consequence of that is defined at the OS level.
Inter-process communication (and recognizing the deletion of an external
storage unit falls under that) should be asked about in a newsgroup for
your platform. See the FAQ for suggestions on that.

V

 

[Rolf Magnus]

How would one go about testing for the deletion of a file that sits
under an o[f]stream object?

There is no standard way to do that. On some operating systems, that can't
even happen, because files are not deleted as long as there are still some
references to them (including open file streams).