Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

Re: Modules as executable scripts?

by friedo (Prior)
on Jun 15, 2007 at 02:14 UTC ( #621383=note: print w/replies, xml ) Need Help??

in reply to Modules as executable scripts?

I typically do this:

package Runnable; sub do_something { ... } __PACKAGE__->do_something unless caller; 1;

Then I can execute the module itself as if it were a script. This is great for command-line tools that need to use inheritance or other OO-ish stuff. For a current project, I have my entire Test::Class-based test-suite implemented this way, so the test classes can be run as if they were .t files, but they inherit parent class tests.

Update: Here is a node that discusses this technique in more detail: How a script becomes a module

Replies are listed 'Best First'.
Re^2: Modules as executable scripts?
by bsb (Priest) on Jun 15, 2007 at 03:25 UTC
    For PAR compatibility I use:
    __PACKAGE__->do_something(@ARGV) if !caller() || caller() eq 'PAR';

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://621383]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (5)
As of 2022-01-22 22:00 GMT
Find Nodes?
    Voting Booth?
    In 2022, my preferred method to securely store passwords is:

    Results (63 votes). Check out past polls.