|Do you know where your variables are?|
Good points. I can stretch my imagination and come up with cases where wanting to lock out duplicates at compile time might be useful. But I agree that such seem quite unlikely and the appeal is mostly an "earlier is better" feeling that is misguided in this case.
But this did inspire me to encapsulate a very simple, reusable method of locking out multiple instances of the same script:
Simply save this to Highlander.pm where you keep your Perl modules and 'require Highlander;' in any scripts that you don't want more than one instance of running at an given moment.
Name stolen from •Highlander.
Note that you can copy the script to a different name or directory if you want to run another instance of it (which you can consider a feature or a bug, depending). Also, on Win32 this still isn't a great solution because the exclusive lock causes Perl to simply act as if the script is an empty file so instead of the second instance of the script failing and giving the "quickening" message, it simply ends successfully after doing nothing.
So for some cases it would be nice to make the lock file external. But that makes it more complicated and is left as an exercise for the reader. (:- tye
In reply to Re^3: Never lock $0 inside of a BEGIN block (BEGIN?)