view http://www.jpsoft.com/, V would show the original source of the text -- not the filename of a temp file, which the user probably doesn't care about.
It should be the responsibility of the program creating the temp file to delete it.deleting a temp file on exit should be V's responsibility, not TCC's
That would work in a few cases. But not when you've got multiple pipes on the command line, or if TCC terminated before V.Hmmm! I can think of not-too-costly ways to get around that. When V is started, start a clean-up thread, passing it a pointer to a struct containing V's PID and the file name. The thread would wait for the V process, delete the file, and terminate.
I disagree. V isn't a passive bystander here; it's an active participant in using the file. (And deleting a file once you're through with it is not a particularly onerous chore.)It should be the responsibility of the program creating the temp file to delete it.
That'd be like the city coming out to fix the water meter at your house, digging a huge hole so they can get at the surrounding pipe and then leaving saying... "It was just a temp hole, you fill it."
I think that depends on whether the file may be opened again. The docs say that further attempts to open it will fail if DeleteFile has marked it for deletion.If there is some way to know when V has opened a handle to the file, then AnrDaemon's approach would work too.