in reply to best way to pass data

I fear you have a mistake in your concept. Why dont you put the 'scripts.pl' functionality into a module and call it then from you main script. Thats what suggested above.

Read the perlmodtut. Its soo simple, here an example.

In Scripts.pm 
 package Scripts;

 sub do_something {}

 1;

[download]
in main.pl. 
 use Scripts;

 my @ARRAY = <DATA>;

 Scripts::do_something( \@ARRAY );

[download]
E voila !
Murat

edited by ybiC: remove <pre> tags, format with <p> and <br /> tags instead, to eliminate lateral scrolling

Replies are listed 'Best First'.
Re: Re: best way to pass data
by rishard (Initiate) on Aug 23, 2003 at 16:08 UTC
    The reason I listed the response dated Aug 23, 2003 at 04:40 is that the Master.pl runs very fast. One of the calls in in a loop so this will call several instances of Slave.pl which quieries outside databases and has a long delay. I do not want to hold up Master.pl waiting on Slave.pl, I just want things to go. In my second need for this, Master2.pl calls and sends data to three different concurrent processes. Master does not need to know the success or failure of the processes, that is taken care of by a seperate process.
    rishard
[reply]

In Section Seekers of Perl Wisdom