One suggestion... if you store the variables you need in a big hash you could do things like iterate over the hash to get all the variables you need. You could then use something like Data::Dumper to serialize the hash and pass it off to the second CGI.
Ideally, however, I would suggest making the functionality of the second cgi into a library, then you could just call the code from that one directly without executing another script and futzing the data around. If you need them to run in parallel you could use fork.
Modulizing the second one would ideally be the way to go... otherwise you either have to serialize the data for the second, or pass it all in as parameters... very ugly for large lists.
- Ant
- Some of my
best work - (1 2 3)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.