On Tue, 25 Sep 2001 [EMAIL PROTECTED] wrote:
> > On Tue, 25 Sep 2001 [EMAIL PROTECTED] wrote:
> > > I generally agree. But if you have a perl script that is not a module, I have
> > > found "do" to be very useful in certain circumstances.
> >
> > How does its execution differ from using system or forking?
>
> "do" executes inline. The called script has access to all the perl
> globals in the calling script. Doing a "system" (which does an
> implicit fork) creates a separate process. Which method is better
> depends on your application.
But in the case of having one daemon spawning another, would 'do' do the
trick? I thought the idea was to create a separate process.
-- Brett
http://www.chapelperilous.net/
------------------------------------------------------------------------
The sudden sight of me causes panic in the streets. They have yet to learn
-- only the savage fears what he does not understand.
-- The Silver Surfer
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
