http://qs1969.pair.com?node_id=104182


in reply to Re: Re: Not Matt's Scripts
in thread Not Matt's Scripts

Just write the functionality of the script as a module and put "standard usage" of it at the end like:

package main; require File::Basename; File::Basename->import( qw(basename) ); if( &basename( $0 ) eq &basename( __FILE__ ) ) { require CGI; my $q= CGI->new(); # ... }
that way you can make one file that is both a module and an all-in-one CGI script. This might even help the modulephobic slowly learn to like modules. (:

        - tye (but my friends call me "Tye")

Replies are listed 'Best First'.
Re: Not Matt's Scripts
by simonm (Vicar) on Aug 13, 2001 at 02:49 UTC
    I've used a similar trick in the past, but rather than checking basename(), it's "unless ( caller ) { ...}", which seems to be equivalent.

      Ah, yes. Much better! I was also thinking of an improvement to prevent the example code from sticking around when it wasn't being used. For example:

      package main; BEGIN { my $isScript= ! caller(2); sub _isScript() { $isScript } } if( _isScript ) { require CGI; my $q= CGI->new(); # ... } undef &_isScript;
      would still require that the sample code be parsed the first time that the module is used but the optimizer would know to throw the resulting code away. Not quite as pretty, though.

      Another hack to prevent even the work of parsing can be done:

      package main; unless( caller ) { my $code= do { local($/); <DATA> }; my $file= __FILE__; my $line= __LINE__ + 5; eval "\n# line $line $file\n$code; 1" or die "$@\n"; } __END__ use CGI; # ... __END__

              - tye (but my friends call me "Tye")