From: Miklos S. <mi...@sz...> - 2005-05-17 12:35:38
|
> I think doing this would help a lot, since I can then keep track of > the original path in the filehandle field and use that to know which > file I am working on. As things stand now, after the unlink step, the > file is not really usable any longer. Yes, but why would you want to use "hard_remove" anyway? If you don't actually remove the file, it's very tricky to handle correctly, since another file may be created with the same name, etc... > I can't even close it and clean up. You can, since release() is already called with the right file handle. I think the current philosophy is that, if you use "hard_remove" and remove open files, then expect things to be broken. Miklos |