I don't get why you make it separate scripts, I'd just let one script both scan for errors and do something with that list.
Otherwise, you'll have to serialize the array to pass it to the other script. Traditionally there are a few approaches: if they're typically all a single word, just pass them along the command line. Or you could pipe the array, one item per text line, into the second script. Or if all that fails, dump it in a serialized format (flat text file, CSV, JSON, XML, Data::Dumper, or Storable) and and pass that, either by pipe or in a file of which you pass the filename, to the second script.
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.