This is probably (I didn't look the source code) an usual unix to windows porting problem: on unix (posix?) an open file can be first removed (unlinked) and then closed while on windows an open file can not be removed.
In our case the temporary file is open, then it is tried to be removed which fails (obviously there is no check if the remove call was successfull) and then the file is closed. This is why remains in the current dir after sed termination. I propose to submit the requet (even better: prepare the patch) to the original GNU sed developers. If they'll fix it the problem will be solved once for ever. In other case the fix has to be done on GNUWIN32 port and repeated for each new release. Borut On Wed, Jun 13, 2012 at 11:16 PM, Anton Shepelev <anton....@gmail.com>wrote: > Charles Calvert: > > > Looks like a temporary file that isn't being > > cleaned up. > > Yes indeed. But whom to contact about the problem? > It seems to be GNUWIN32-specific... ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ GnuWin32-Users mailing list GnuWin32-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
