in reply to Re^3: Win32: Setting a layer with binmode causes problem with close() on Windows (PerlIO silently fails to close the file)
in thread Win32: Setting a layer with binmode causes problem with close() on Windows
So, the fact that system has returned does not mean all of it resources have been cleaned up.Oh my! I didn't think about this issue! But this would mean that it is unsafe to have an (external) process create a file, and then use it in my program - at least under Windows, which is very picky about this kind of stuff? If I understand you right, this should even true if we use IPC::Run to run the process. OTOH, this scenario - running an utility to create a file, then use it - is so common, that I wonder why we are not bitten by this more often. Or is there a clever, safe way to achieve the goal?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^5: Win32: Setting a layer with binmode causes problem with close() on Windows (PerlIO silently fails to close the file)
by BrowserUk (Patriarch) on Jun 17, 2013 at 13:23 UTC | |
Re^5: Win32: Setting a layer with binmode causes problem with close() on Windows (PerlIO silently fails to close the file)
by Anonymous Monk on Jun 17, 2013 at 13:00 UTC | |
by BrowserUk (Patriarch) on Jun 17, 2013 at 13:26 UTC | |
by BrowserUk (Patriarch) on Jun 17, 2013 at 13:38 UTC | |
|