Not to sound discouraging, but this is an idea which is often considered, but usually shouldn't be. Whenever you find yourself needing to do something "tricky", you need to step back and ask yourself "what problem am I trying to solve"? I have, on far too many occassions, found myself working on a solution without bothering to reconsider the question when someone else comes along and points out a much better way to solve my problem.

So, what problem are you trying to solve? As far as I can tell, you're saying "here's my solution. How do I implement it?" Since you're not sure how to implement it, you're really not sure that you have a solution! :)

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

--
Cheers, Joe

If your first CGI is modular, e.g. it has a sub you can call that produces results, you could add a "1;" to the end of the script, then require it into your first CGI and call the sub. Or you can wrap the body of the script into a sub and then require/import and call your sub.

For example, I had a few small scripts where I wrapped them in a sub something like:

#!perl -wT
use strict;
use CGI;
# use more modules;

&mysub1();
exit 0;

sub mysub1 {
# the body of the script
}
1;
[download]

--
hiseldl
What time is it? It's Camel Time!

The way I've done this is to have the first CGI script generate a form, which then calls the 2nd

Alternatively, you can look at using redirects

But, uhhhh... this isn't what you want is it:

open FH, "/path/to/secondscript.cgi|"; # note the pipe!
print join '', <FH>;
close FH;
[download]

--nutshell