On Sat, 24 Mar 2012 20:48:47 +0100, Walter Bright
<newshou...@digitalmars.com> wrote:
On 3/24/2012 12:36 PM, Walter Bright wrote:
On 3/24/2012 12:31 PM, Nick Sabalausky wrote:
Windows is known to enjoy holding locks on files just for the fuck of
it.
See if the behavior changes if you add some delay just before the last
line.
Or, if you adjust it so that compiling test.d takes longer.
I tried those. No dice.
Even running a program in between that does a sleep for a full second
does not fix it.
You could try Process Explorer or
http://blad.wordpress.com/2006/05/11/fuser-on-win32/
to find out who is locking the file.
