I agree. Here is some history, FWIW: Executing one script with another

UPDATE: Ack! I see now that MonkPaul listed the node, but didn't actually link to it. Sorry for being redundant.

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

I was trying to get this first script to get the input from either the command line or web page.

Based on the input, being either two files or a single sequence, one of two scripts would execute, called from within the first cgi script.

MonkPaul.

Why don't you convert the script's guts into a module, and write two simple interfaces (CGI and commandline) which use the module?

# script.cgi

use CGI;
use BlastTool;

... get info from CGI object ...

BlastTool::do_it(
   $date,
   $show_filter,
   ...
   \@chromo_filter, 
   \@advanced_filter
);
[download]

# script.pl

use BlastTool;

... prompt the user for the info ...

BlastTool::do_it(
   $date,
   $show_filter,
   ...
   \@chromo_filter, 
   \@advanced_filter
);
[download]

Arrays are passed by reference to avoid being flattened.

I suppose that is one option.But i have a load of other modules to call from within the BlastTool.cgi script.

I was just trying to do this to try and learn how to execute another script really so i know personally what i am doing in the long run.

Over all i have

ComLine.pm
MergeFiles.pm
parseFiles.pm
Email.pm
Filter.pm
FilterHeader.cgi
runBlast.cgi
[download]

I was just trying to get the first script to be an input one, then actually perform the tasks after the input has been gathered.

I have really ballsed up the writing of this code as its currently all in one cgi file with separate functions, so i am in the process of trying to split it all up and get it to work properly from within different modules. Im ok with calling the modules from within the BlastToolcgi, but i just wanted to get the input in a separate script and possibly implement a loading page too.

Argggggggghhhhhhh, what have i done!!