Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Re: Re: Never lock $0 inside of a BEGIN block (Win32?)

by zby (Vicar)
on May 22, 2003 at 08:08 UTC ( #260003=note: print w/replies, xml ) Need Help??

in reply to Re: Never lock $0 inside of a BEGIN block (Win32?)
in thread Never lock $0 inside of a BEGIN block

For me the fact that this problem appeares only on Win32 machines makes it only worse. It obscures the view.

By the way why should one need to do it in the BEGIN block? I mean for sure there must be some cases where it is needed, but for most cases it is just a automatic thought, something like that: It should be locked early, early is linked in your brain with the BEGIN block - so put it into it.

  • Comment on Re: Re: Never lock $0 inside of a BEGIN block (Win32?)

Replies are listed 'Best First'.
Re^3: Never lock $0 inside of a BEGIN block (BEGIN?)
by tye (Sage) on May 22, 2003 at 15:37 UTC

    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:

    package Highlander; use strict; use warnings; use Carp qw( croak ); use Fcntl qw( :flock ); # LOCK_EX LOCK_NB sub import { croak( "The Highlander does not appreciate being 'use'd.", " Please simply 'require' the Highlander.\n" ); } if( ! defined fileno *main::DATA ) { croak( "No __END__ in sight. Please put an __END__", " to $0 (or 'require' the Highlander; don't 'use')\n" ); } flock( *main::DATA, LOCK_EX|LOCK_NB ) or die( "The Highlander feels the quickening.", " Another $0 is already here.\n" ); "There can be only one!";
    Simply save this to 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

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://260003]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (3)
As of 2018-03-24 05:25 GMT
Find Nodes?
    Voting Booth?
    When I think of a mole I think of:

    Results (297 votes). Check out past polls.