comment on

Rather simpler would be to run an asynchronous perl one-liner at the end of the script that waits a couple of seconds for the script to terminate and then deletes it like this:

P:\test>type junk.pl
#! perl -slw
use strict;

sleep 10; ## Simulate doing stuff

## Start an asynchronous perl one-liner
## sleep a couple of seconds and the delete the script ($0)
system 1, qq[ perl -e"sleep 2; unlink'$0'" ];

P:\test>junk

P:\test>dir junk.pl
 Volume in drive P has no label.
 Volume Serial Number is BCCA-B4CC

 Directory of P:\test

File Not Found
[download]

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.

In reply to Re: Deleting the Currently Running Script in Win XP by BrowserUk
in thread Deleting the Currently Running Script in Win XP by Dru

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks